Changelog -
v.01
-Removed: Torch.
-Installation: shortened ascii on updater-script
-Fixed radio
-Fixed Camera (Use ActionSnap)(You can get MIUI camera viewfinder to work it just wont' write the files correctly atm. After opening MIUI Camera change settings > picture size to 3MP)
-Broke altdrawer. Sorry. APK invalid. remove from system/app and install from attatchment if you want it; i'll fix it for .02
-Maybe some more things...
v.00
-Ported
2nd update up..
No camera, Sorry. Havn't been able to test wifi. Will remove torch.apk and various others... Would also like to hcange data config for launcher to default 3d cube animations and to default the appdrawer to grid rather than list...
Lots of Espanol > Engles translations still needed...
Credit to: MIUI team, XDA, Rdanner, Jorgonv, sferrariba(defy thread poster)
Link to original thread I found.
http://forum.xda-developers.com/showthread.php?t=1238592
Download:
v.01http://www.mediafire.com/?fbg3860xvcr5is7
v.00http://www.mediafire.com/?ig4r0oes9m4ja8w
Wipe your data/cache and dalvik just incase,
apply update
I'd like to go to that day that the camera works in gingerbread roms for bravo!!
I really would like to use gingerbread in bravo, Im coming from Cliq XT and Backflip (Well, I still have them both) and they have fully working gingerbread roms!
Well the only thing we can do is wait till @rdannar or some else get the camera working!
Ya i'll work on the camera too soon i'll be honest he's going to have a better clue than I am...
I found a 2.2 sense rom for the defy i am going to try to port so that that way we can have a little Rosie/SenseUI too...
after that i'll probably try to see whats up with the camera,
i believe if i can ddms the forceclose on the camera i can read up a bit on that too and see whats up; i pmed rdanner about what camera modifications particularly he noticed were needed for his msgingerblur cause that's android 2.3.4 aswell,
for a camera i suggest msgingerblur or the stock froyo diet thing rdanner made
rubbachicken said:
Ya i'll work on the camera too soon i'll be honest he's going to have a better clue than I am...
I found a 2.2 sense rom for the defy i am going to try to port so that that way we can have a little Rosie/SenseUI too...
after that i'll probably try to see whats up with the camera,
i believe if i can ddms the forceclose on the camera i can read up a bit on that too and see whats up; i pmed rdanner about what camera modifications particularly he noticed were needed for his msgingerblur cause that's android 2.3.4 aswell,
for a camera i suggest msgingerblur or the stock froyo diet thing rdanner made
Click to expand...
Click to collapse
At this point, people need to stop relying on others to get a Defy rom, any Defy rom (CM7 nightlies, MIUI weekly update, regular roms that regular developers made), to work on the Bravo. It is a very simple process.
1) Open ROM in Winzip
2) Delete all the folders and files except for "system"
3) Download this
4) Extract files "motorola" and "META-INF" to a known location
5) Move extracted "META-INF" to / (root) of the ROM
6) Delete folder "motorola in /system/ect
7) Move extracted "motorola" to /system/ect
Not to be a **** but did anyone have anything useful to post?
Fixed camera same story as w/ rdanners only works w/ 3rd party so far miui camera not working actionsnap is though new upload coming soon
rubbachicken said:
Fixed camera same story as w/ rdanners only works w/ 3rd party so far miui camera not working actionsnap is though new upload coming soon
Click to expand...
Click to collapse
Can't wait to try it with the 3rd party app workaround. And thank you! Seems now a days too many people don't appreciate the work people put out there if it isn't perfect. Up until now no rom is perfect. I have a Droid Incredible and the dev community is pretty big, a lot of roms for it and all still have bugs here and there. Keep up the work. I know there is a lot of people out there that don't really post but really appreciate any work you are doing for the Bravo community
One thing I'm having an issue with is settings for the apks...
for example when you select a 3d effect for the launcher, it saves the file in /data/data,
i can get /data/apps to copy over frm the update-script but all attempts so far to get /data/data over havn't worked (since it's copying /data i assumed it would copy /data and it's subdirectories aswell), i've tried to unpack the apks and change the default settings then repack them, that's how I broke altdrawer in .01...
Does anyone have a thought on this? is it likely there is a script clearing /data/data on first boot?
Primarily I want to make folders for the launcher, and put all the icons in them... I found the workspace.xml file that lists the x/y coords of the icons etc... but I can't seem to get any changes to affect it ... (This was found inside the apk)
BravoMotorola said:
At this point, people need to stop relying on others to get a Defy rom, any Defy rom (CM7 nightlies, MIUI weekly update, regular roms that regular developers made), to work on the Bravo. It is a very simple process.
1) Open ROM in Winzip
2) Delete all the folders and files except for "system"
3) Download this
4) Extract files "motorola" and "META-INF" to a known location
5) Move extracted "META-INF" to / (root) of the ROM
6) Delete folder "motorola in /system/ect
7) Move extracted "motorola" to /system/ect
Click to expand...
Click to collapse
I agree on this. While it won't get the camera working, it is still a more proper way of making a port. Still reading up on android development (as I got older I get less inclined to do something without understanding what I am doing first) but as a system builder I know it's better to make a new system from scratch rather then taking an image from one machine and sticking it on another. Too many things break that way
Sent from my HTC Glacier using XDA App
Sorry haven't gotten around to pm and stuff.. work a lot on weekends
@ rubbachicken
What did you do to get camera working? I think I know but would be good for others to know also.
For copying data you need to first delete data recursive then make sure the correct folders have correct permissions after you copy them in the script.
Or you may have to make a tmp folder and do a package extract to push folders on but set permissions to write into data
Not sure about permissions, then download yaffs explorer from market and it has a setting to show what permissions are needed for each file and folder.
@dontbejeff
You are right... it is better to start from a vanilla build made for bravo. But that is some serious coding for a device that doesn't even have a leaked gingerbread rom like defy. If we ever had a leak or something similar then camera would be easy...
That is how I figured out this much of camera by working with froyo stock roms first (T-Mobile). To figure out what is different in the roms.
Sent from my MB520 using XDA App
rdannar said:
Sorry haven't gotten around to pm and stuff.. work a lot on weekends
@ rubbachicken
What did you do to get camera working? I think I know but would be good for others to know also.
For copying data you need to first delete data recursive then make sure the correct folders have correct permissions after you copy them in the script.
Or you may have to make a tmp folder and do a package extract to push folders on but set permissions to write into data
Not sure about permissions, then download yaffs explorer from market and it has a setting to show what permissions are needed for each file and folder.
@dontbejeff
You are right... it is better to start from a vanilla build made for bravo. But that is some serious coding for a device that doesn't even have a leaked gingerbread rom like defy. If we ever had a leak or something similar then camera would be easy...
That is how I figured out this much of camera by working with froyo stock roms first (T-Mobile). To figure out what is different in the roms.
Sent from my MB520 using XDA App
Click to expand...
Click to collapse
YES, that information would be great. Then we could get working camera on CM7 and other Defy roms. PLEASE, rubbachicken give that info!
ui_print("[*] Copying Apps");
package_extract_dir("data", "/data");
ui_print("[*] Setting Permissions");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
set_perm_recursive(1000, 1000, 0777, 0776, "/data/local");
make sure you use the correct mount for the data wich depends on what updater binary you are using
i am pretty sure he moved over the com.camera.jar
the etc/camera permissions files.
and the 3 camera etc files in main etc folder.
cheers
rdannar said:
ui_print("[*] Copying Apps");
package_extract_dir("data", "/data");
ui_print("[*] Setting Permissions");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
set_perm_recursive(1000, 1000, 0777, 0776, "/data/local");
make sure you use the correct mount for the data wich depends on what updater binary you are using
i am pretty sure he moved over the com.camera.jar
the etc/camera permissions files.
and the 3 camera etc files in main etc folder.
cheers
Click to expand...
Click to collapse
I must still be a major noob, what's the first part of your post about?
BravoMotorola said:
I must still be a major noob, what's the first part of your post about?
Click to expand...
Click to collapse
ui_print("[*] Copying Apps");
displays: Copying Apps...
package_extract_dir("data", "/data");
extracting files from .zip directory "data" to phone directory "/data"
ui_print("[*] Setting Permissions");
displays: Setting Permissions...
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
setting permissions for all files is "/data/app"
set_perm_recursive(1000, 1000, 0777, 0776, "/data/local");
setting permissions for all files is "/data/local"
Here is some MIUI straight from MIUI team. It has the camera working (ALL RUBBACHICKEN'S WORK, and in the same condition) And it is full English (fixes one of his problems)
MIUI.us_MB520_1.8.19_Eng.zip
All credit to rubbachicken
I have to be honest i'm not sure exactly what I did ... I copied over the etc/permissions files that were relevant to the camera, also replaced all the libsocameraclient and whatever else I could find, the mot_ise_imager or something like that was replaced too, i'll make a more specific list of files tomorrow...
I was up till 5am last night so i'm kinda on break today haha...
thanks for the help w/ the permissions etc, i wasn't sure what permissions to set for the /data/data
Info for what I did to get the camera working; (As best as I can remember, and applied to CM7 and tested.)
found here;
I have recieved a bit of credit for this from the bravo community and i'd like to just mention real quick that i primarily just copied and pasted, if files were edited to make this work beyond which files are there, that was probably rdanner or walter devs... I have a feeling I gathered some files from rdanners gingerblur since it was working....
Maybe that's where I got the com.motorola.camera.xml and .jar found in /etc/permissions and /system/framework
I know i directed my attention to that because it's a GB rom w/ camera working.
Anyway, theres the instructions I followed...
Great job doing miui. Main files is mot. Sh file in etc. then egl libs.. At this point the camera.jar does nothing... Permissions probably dont make huge difference. Egl, gles. Gls files all do.
Surface flinger.so does also but that is okay due to similarities with defy
Sent from my MB520 using XDA App
Related
Made a new thread for the update.zip versions of the LagFix since i have had people asking me to do that so it doesn't get cluttered up together with RyanZA's fix in his thread.
Only one file included... Will overwrite old root version.
Testet on firmware: (Did a fresh reflash every time)
I9000:
I9000XWJG5 (Eclair - Europe)
I9000XWJM1 (Eclair - Europe)
I9000XWJM5 (Eclair - Europe) (Thanks Peaster111)
I9000XXJP2 (Froyo - Europe)
I9000JPJG8 (Eclair - Africa)
Captivate: (Thanks to Zilch25 for testing)
I897UCJH2
I897UCJH3
Instructions:
(Note that i recommend that you do a fresh reflash through ODIN.)
1. Download the update.zip of your choice and rename it to update.zip.
2. Place it on your internal sdcard.
3. Turn off your phone.
4. Hold down Vol Up+Power button+Home Button for a couple of seconds until u see the galaxy logo .
5. Use the up and down buttons to get to update.zip.
6. Press menu button on update.zip to select it.
7. After install, the phone restarts.
8. Go to the newly installed 'SL4A' application from the app list, open it and choose either LagFix_Ext2.sh or LagFix_Ext4.sh to install the fix.
9. The script should run takes around 2-4 mins before it reboots.
10. First reboot after applying script will take some time as it's moving data around and mounting folders.
Regarding Step 4: What is written is for GT-I9000 version.
For Captivate and Vibrant as other people with that phone.
For Captivate people that are trying this on I897UCFJ6 please read the following post: http://forum.xda-developers.com/showpost.php?p=7939738&postcount=177
Notes:
The current version works on Froyo BUT you can only use the ext2 option as the current kernels in Froyo doesn't support ext4.
Known Bugs:
Got no idea if people still will have problems with changing fonts with ext2 since it works for me.
Credits:
RyanZA - Original bat fix
husq510 - Supplied files needed to enable ext4 support
Zilch25 - For being my test subject on the Captivate board
Donations:
Had a few people ask for donation link so here it's: Donate
Do note though that you don't have to donate if you don't want to.
Changelog:
v.2.3.3
Minor bug fixes.
Put all into one file that will remove old root and reapply new root in the same zip file.
v2.3.2
Removed custom hosts file for ads blocking as that was the problem with SL4A crashing.
v.2.3.1
Changed version of SL4A which should fix the FC that SL4A is giving.
v2.3.0
Scripts redone to do all moving of data on boot to minimize chance of loosing applications and settings.
Firmware check added to scripts to check if your firmware needs GPS Logging fixed.
Removed support for Ext3 as there is no reason to have it since we can use ext4
Added custom apn-conf.xml file for APN settings.
Added hosts file for blocking ads.
v2.2.2
This fix is for Captivates running firmware I897UCJH2
Turns off GPS logging and removes whatever logs that might already have been made
v2.2.1
Fixed old bug with /data/app-private
Added checks to scripts so they check if your system has support for the filesystem you choose
v2.2
Added Check_Space.sh to sl4a
Added support for ext4 (Only works on eclair builds)
Busybox 1.17.1 is NOT required anymore, but is the version i'm including.
v2.1
Based on RyanZA's v2.3
Added support for ext3 (Only works on eclair builds)
Removed support for /dbdata/databases
Changed /data/app-private from mount to symlink
Added two versions of the zip's. One for people who already have a rooted SGS and one that will root the SGS.
v2.0
Based on RyanZA's v2.0
Initial release.
Added support for /dbdata/databases
Added support for /data/app-private
Hey, would you like me to test this on JP3??
Thread
is it possible to undo this lag fix? what scores in quadrant are we expecting with this?
All lag is gone with this or is there some left as I encounter in ryan's? tnks in advance for the hard work
Hi
Great tool
if i'll replace files in the zip will it still work?
(like replacing busybox with version 1.18 and replacing apn-conf with one who has Israeli carriers or adding fonts library for hebrew fonts)
Thread Astaire said:
Hey, would you like me to test this on JP3??
Thread
Click to expand...
Click to collapse
You are welcome to test it on JP3 if you want to but just remember Clockworkmod Recovery can have problems with applying the update.zip's
rbanaco said:
is it possible to undo this lag fix? what scores in quadrant are we expecting with this?
All lag is gone with this or is there some left as I encounter in ryan's? tnks in advance for the hard work
Click to expand...
Click to collapse
There is a script included to remove the lagfix. From test with stock kernel quadrant score is excepted to be around 2100-2200 with ext2 and 1800-1900 with ext4.
From all the testing we have been doing on this release when fixing bugs there haven't really been that much lag... you might see small lag when opening an application for the first time or when installing an app since we are using a different method this time where we don't move the application's apk's after it's installed, but personally i haven't seen this yet.
omrij said:
Hi
Great tool
if i'll replace files in the zip will it still work?
(like replacing busybox with version 1.18 and replacing apn-conf with one who has Israeli carriers or adding fonts library for hebrew fonts)
Click to expand...
Click to collapse
Hmm no idea tbh... You might be able to open the zip, replace the files and close it again without losing the signature that it's signed with, but this is something that i haven't tried yet so don't know if it will work.
thanks for the answer.. one more question if you don't mind answering.. what would you advise ext2 or ext4? which provide better performance despite of the score? thank you
rbanaco said:
thanks for the answer.. one more question if you don't mind answering.. what would you advise ext2 or ext4? which provide better performance despite of the score? thank you
Click to expand...
Click to collapse
I would recommend ext4 since it have journaling, which means there is a smaller chance on losing data if your phone lose power by pulling the battery or if the battery reach 0%.
Other people would say ext2 since ext4 might reduce the lifetime on the NAND since it has journaling
I have only tested the ext4 myself pretty much while i have had others to test both ext2 and ext4. Also this is what Zilch25 has posted about ext2 and ext4 on the captivate forum:
Is EXT2 for me?
If you want your Quadrant scores to be bloated beyond belief and don't care if your data spontaneously combusts (Results may vary). Alternatively if you're worried about your NAND wear leveling not being able to handle the strain of EXT4 journaling.
Okay EXT2 is scary, how about EXT4?
You can't afford for your things to get corrupted? Weirdo. Real world performance between EXT4 and EXT2 is barely noticeable if at all, for the everyman this is probably your best bet.
Click to expand...
Click to collapse
omrij said:
Hi
Great tool
if i'll replace files in the zip will it still work?
(like replacing busybox with version 1.18 and replacing apn-conf with one who has Israeli carriers or adding fonts library for hebrew fonts)
Click to expand...
Click to collapse
i think u can replace or delete files as u like.
i replaced, delted or added files every time before i flashed a new ROM, like HACKECLAIR or SamSet.
Works well.
applying ext4 gives me the stopped unexpectedly google error
Yeah I can second that... after a full wipe SL4A is giving me FC's now too =P
Just wanted to add:
EXT2 may be less safe than EXT4, but to-date, there has been no reports of any corrupt or lost data using the EXT2 fixes. This is over a pretty huge sample over a fairly long period. Not to say there are no problems with EXT2, but there has not been any impact to anyone for using EXT2 as yet.
Other than that, awesome job Tayu! Looks great!
yep, i get the force close for either script from sla4
OK ill reupload with the old version of sl4a then.
Im still not sure wether i should go for Ryan's one-click .apk fix or this one.
Anyone tested this one on I9000XXJM2? wich is stock firmware for me.
Tayutama said:
OK ill reupload with the old version of sl4a then.
Click to expand...
Click to collapse
v2.3.1 uploaded which replaces sl4a_r1 with sl4a_r0 which was the one used in the older versions of the fix. Should fix the problem with getting force close
Tayutama said:
v2.3.1 uploaded which replaces sl4a_r1 with sl4a_r0 which was the one used in the older versions of the fix. Should fix the problem with getting force close
Click to expand...
Click to collapse
Applying it now, I'll let ya know how it goes
do i need to remove the previous sl4a?
A.VOID said:
do i need to remove the previous sl4a?
Click to expand...
Click to collapse
would be the best as they each got a different name.
If you got root explorer you can remove it from /system/app
It's called: sl4a_r1.apk
Tayutama said:
would be the best as they each got a different name.
If you got root explorer you can remove it from /system/app
It's called: sl4a_r1.apk
Click to expand...
Click to collapse
Yeah you might need to... I just reapplied without removing it and only r1 shows up =P
Tuxility in the market http://www.appbrain.com/app/tuxility/com.grimmvarg.android.tuxility
News: I have discovered that editing the settings.db is not very usefull and might make your system unstable. I have therefor decided to choose a less generic way of letting users access edit system settings, like wifi sleep time etc.. Should be done in a day or two
The userbase has grown a lot these last days, which means a lot more feedback. No big bugs as of yet, but please post any issues you find, so I can fix them And off course feature requests!
Tuxility
Hey guys!
Im creating an app for the Samsung galaxy s, Ive only been working on it for a few days, but a few features have found there way into it:
- Flashing a kernel without pc, while phone is on. ( ref: http://forum.xda-developers.com/showthread.php?t=765724)
- Back up your current kernel
- Phone codes (view battery stats and various tests of hardware)
- Backing up and restoring /efs
- Reboot to Recovery, Download and standard mode
- Cleaning battery stats
Features to come:
- Toggle Mediascanner on/off
- Editing system settings
- Full System information
- Change system Font
- Sensor dump (for fun)
- Improved GUI, with colors and an icon
- Place backups on external_sd if it exists (thanks _renaud_)
- Add tools for calibration of screen/battery etc..
Requirements:
- Root
- A Samsung Galaxy S (all variants) running Android 2.1 and up.
Why am I releasing this?
Well for one to share the kernel-flashing feature (thanks to supercurio for this). Also to get feedback on what works and not. But more importantly to get feedback on what to add or change about feature and code (which is located here, yes I know my github tree is suboptimal ). I'm used to Java but pretty new to android. So any feedback on the code is appreciated
NOTES ABOUT THE KERNEL FLASHING
I hacked together a filechooser to pick the zImage you want to flash. And you can flash only zImages or Tars including zImage.
The filechooser sets /sdcard/download/ as starting DIR so i suggest you unpack your zImage there. Bakups are stored in /sdcard/.tuxility/backup
And the notice of no responsibility
I take no responsibility if my app breaks your phone, (not that it should, but now i said it) and you try this software at your own risk. On a related note, the code and the app is released under GPLv3. I will however, do all i can to help
Logging is on, so have a look in logcat if something is not working and let me know
I hope someone will find this usefull, and find the time to give me som feedback
Known issues:
The settings file seems to be located elsewhere on the galaxy tab. So if anyone with a tab wants to help me out finding this, that would be great
If flashing kernel fails, and log show "not enough space on device" remove any folder in /cache named "2010-*" that contains a zImage. This is fixed irelease 1.2, I thought that /cache was cleaned at boot, but this was not the case.
The way that all this work
The backup features are pretty straight forward, using a system shell I give a cp/cat/tar command wherever it is suitable. For instance /efs needs to be tared to keep uid and permissions.
For reboot i issue the "reboot <mode>" as root
The kernel install uses the procedure from this thread http://forum.xda-developers.com/showthread.php?t=765724 and copies a binary file to /apps and uses it to install the new kernel image.
All backups are stored in /sdcard/.tuxility/backup
A SMALL WARNING
Just like anyone will tell you, remove all lagfixes when flashing a new kernel if you are not _sure_ that the new kernel you are flashing support your old lagfix, ktnx
CHANGELOG
V1.2
- Huge code cleanup
- Now using flash_image to flash kernel, thanks to koush!
- no more screen distortion after flash
- No forced reboot after flash
- Better execution controll
- Added phone codes
- Removed edit settings.db (this is to risky, no replacement on the sketch board)
- Starting on feature to fetch latest kernel
V1.1
- Install kernel from tar archive
- Finally have an icon
- A bit more restructuring of code
Android Market will not allow me to use sub 1 versions.. :/
V0.21:
- Restructured the menu, for later additions
- Added remove batterystats
- Backup Kernel now sets date in filename
- Improved filechooser, will not install files with a file extension
- Big cleanup of code
GrimmVarg I will follow your work very closely !
Wow, this is good. CWM doesn't backup the kernel, and with this app, one can easily do it. Would be absolutely wonderful if it can be included in the CWM recovery menu.
Thanks and will try it soon.
Is it somewhat like this?
http://forum.xda-developers.com/showthread.php?t=775154
Regards
miro666 said:
Is it somewhat like this?
http://forum.xda-developers.com/showthread.php?t=775154
Regards
Click to expand...
Click to collapse
Yes and no, Its the same concept but different features, except the Secret codes list which I havent implement and the wiping of batterystats. I used SGStools my self before I started on Tuxility, its a very usefull app.
I am making tuxility mostly to get all the features that i need in one app, as I feel that most of these utility apps both overlap on features and miss a few essential features, like flashing a new kernel for instance. So my goal is for Tuxility to be a feature full alternative that cover all common needs, and in addition has specialized features for a give rom/kernel.
Thus feature requests are most welcome
Can you publish this to Android Market?. Further updates are easier that way. Thanks for making this.
hacksome said:
Can you publish this to Android Market?. Further updates are easier that way. Thanks for making this.
Click to expand...
Click to collapse
Yeah. As soon as I get an icon and rewrite the code for executing shell commands i'll push to market
please flash,
pda
modem
csc
withtout pc, send .apk
thanks
Yeah Mr....
great idea ... bring sgstools, spareparts and some features missing in cwm together ... absolutely welcome!!!
gwaan doin this great job!
My20 said:
please flash,
pda
modem
csc
withtout pc, send .apk
thanks
Click to expand...
Click to collapse
c0llal0 said:
Yeah Mr....
great idea ... bring sgstools, spareparts and some features missing in cwm together ... absolutely welcome!!!
gwaan doin this great job!
Click to expand...
Click to collapse
Yeah, If its possible it would be nice. Ill look into it later. Right now Ive been getting help by mikebeecham to make an icon for the app as i plan to release it to market tonight. But I want to implement the possibility to maipulate the settings.db first. So.. yeah. Hoping to get it done while my girlfriend is at the theater
Install and backup kernel works fine.
Really nice
Just wanted to let you know i used this to flash Supercurio's VooDoo lagfix kernel. Easy and painless!
Thank you for this tool.
Sent from my GT-I9000 using XDA App
Thanks for the super cool all in one app..
looks fantastic - definitely going to give it a whirl!
Just wanted to throw this out there.
This app works on the Galaxy tab as well. trying to view settings causes a FC however backing up the kernal worked
looks great.
backup also csc and eventually modem would be very nice.
socksfelloff said:
Just wanted to throw this out there.
This app works on the Galaxy tab as well. trying to view settings causes a FC however backing up the kernal worked
Click to expand...
Click to collapse
Glad to hear it! Could you tell me if if backing up settings.db work? Might be that this file is located elsewhere on the tab. And if so I need to do some digging to find as I dont own a tab my self
zoubidou said:
looks great.
backup also csc and eventually modem would be very nice.
Click to expand...
Click to collapse
Yeah, after i get settings maipulation to work and get a little bit better look an the app, ill be looking to try and both backup and install full firmware
i just tried a kernel update.
i used speedmod version 11 cwm.
i stated wrong file format. sorry for that.
Please read this entire post!
<<<This is a link to the... FAQ Click it!!>>>
I have created a complete bundle of GingerBread with the newest kernel from GIT (Feb 28 / 1276), and the newest rootfs from GIT (Feb 24).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps!
Directions:
1. Download the full bundle (zip). (Updated Mar. 11 2011)
If instead you just want the system.ext2 (zip) file (updated Mar. 25 2011) by itself... Don't download this unless you know you want to update!!
2. Extract it. You’ll see a folder, GBX0A, copy its contents to the root (base) of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Download the ts-calibration file from this post (should work for RAPH/DIAM) and extract the .zip to where you run haret.exe from - typically the root or 'base' folder of the SD card. Not within any folders, unless you run haret.exe from a folder!
**If you have issues with the above file, you must calibrate manually. To start manual calibration, just delete any ts-calibration files and boot. Sometimes this doesn't work, and you have to use an older kernel from GIT (I found 1225 works well) and generate the ts-calibration file by booting and pressing the 5 zones. Once you have a good calibration file hold on to it (make 15 copies if it's a really good one ), reboot & go back to the newest kernel from the autobuild service! Thanks**
6. Run haret.exe... Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins or so the media scanner can go thru everything, etc. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get newer or archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
In addition, I am using the newest rootfs from GIT - Feb. 10. There are other rootfs options, see F22’s thread if you want to use more keys or move around the home button. Of course, there's always the roofs autobuild service if you want "stock" rootfs images - F22 builds his off of these and modifies them .
See Incremental Updates for more information on this topic of updating!!
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data, Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Obviously this build is Alpha, and there are going to be problems. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
stinebd's original post HERE
Mar. 11 2011 Changelog
Things broken in this build:
libgps - explains itself, no GPS and probably no netloc (cell-tower based location)
HW3D is either not working, or just not preset - I ran neocore and let's just say a lot of textures are missing. Got a ridiculous score, but again - no textures, not much to render haha.
DIAM users have reported the g-sensor is flipped -
emc02 said:
ok, the solution for DIAM100 is:
change "gsensor_axis=2,-1,3" to "gsensor_axis=-2,1,3"
works perfect!
Click to expand...
Click to collapse
This line should be in the startup.txt file if that wasn't obvious .
Thanks to emc02 for that solution!
The keyboard should be fine, but I've had some Blackstone users complain - if you want, switch the keyboard out with another. mr_grisha's original post.
Anything that's broken in Froyo, is probably broken in this build.
Changelog March 25, 2011
Further tuned keyboard sizing to be useful on VGA (also made the key labels bigger)
World-phone settings support (very important for future RIL enhancements especially on CDMA)
Enabled HSPA icon (someone on GSM please let me know if it actually works)
Strange, I never saw the calib. screen. Probably because I just replaced the system.ext2 file and let it run it's course? I do recall there being calib. "issues" with 1253 because the text would continue to scroll even while you were attempting to tap the points.
[R^7Z EDIT]I don't suppose that would work if you were re-working this from the beginning or starting over from scratch (doh!). Lucky me, I save just about every new/update regardless of kernel package or rootfs update[/R^7Z EDIT]
R^7Z said:
Strange, I never saw the calib. screen. Probably because I just replaced the system.ext2 file and let it run it's course? I do recall there being calib. "issues" with 1253 because the text would continue to scroll even while you were attempting to tap the points.
Click to expand...
Click to collapse
If you already have a ts-calibration file, there's no need to create a new one .
A note to all troubled users
And additionally, to those who are reporting issues, it would behoove you to help the devs out by not making them guess what you are using (device) to include but not limited to, which rootfs and kernel package (date of release and commit ID might be helpful). That being said, be aware of what you are talking about (app discussion should not fall into this thread) and please keep talks of neopeek variants to a minimum (I know a little bit about these builds and will help out where I can, PM me if you really think I can help and if you really need some assistance)
arrrghhh said:
[CUT]
HW3D is either not working, or just not preset - I ran neocore and let's just say a lot of textures are missing. Got a ridiculous score, but again - no textures, not much to render haha.
I noticed the (virtual) keyboard is comically tiny. Seems to work fine tho...
[CUT]
Click to expand...
Click to collapse
Noticed the same thing in neocore (30fps without textures) but quadrant 3D tests looked good. Probably we need to test more apps.
Virtual keyboard is unusable on Blackstone. All buttons are tiny and kind of stacked together at the bottom of the screen.
BTW. I can't calibrate the screen since .35 FB commit (17 Dec). I think it's because of FB debug spam - this should be easy to fix.
on ralph100 i've been stuck on "busy" loop for about 20mins now.
loops saying "INFO task rpcrouter: 15 blocked out for more than 120 seconds"
thebranded said:
on ralph100 i've been stuck on "busy" loop for about 20mins now.
loops saying "INFO task rpcrouter: 15 blocked out for more than 120 seconds"
Click to expand...
Click to collapse
Hrm. I'm going to go with format your SD card using the HP Tool. Full format, FAT32.
Also, might want to try kernel 1258. Let me know if neither of those things improve it. Is it creating a data.img...?
g3rm0 said:
Noticed the same thing in neocore (30fps without textures) but quadrant 3D tests looked good. Probably we need to test more apps.
Virtual keyboard is unusable on Blackstone. All buttons are tiny and kind of stacked together at the bottom of the screen.
BTW. I can't calibrate the screen since .35 FB commit (17 Dec). I think it's because of FB debug spam - this should be easy to fix.
Click to expand...
Click to collapse
Sorry forgot to respond to this. Two things, there's an app called "gingberbread keyboard". Find it on the market, see if it works better for you.
Second, I've heard the new 1258 kernel is fixed - not sure how, but it seems the clocks commit from jb's tree did it.
works with 1258, did reformat SD card.
Still had issue with not seeing the touchscreen calibration though, just copied over a old TS file.
thebranded said:
works with 1258, did reformat SD card.
Still had issue with not seeing the touchscreen calibration though, just copied over a old TS file.
Click to expand...
Click to collapse
Glad it's working for you. I think we've narrowed down the calib issue, so hopefully we'll get that fixed for all devices soon. Not sure why but RHOD's don't seem to have the issue any longer - no matter, we will get it resolved for all devices. Sometimes just takes longer for the old devices unfortunately...
[xda Link] Gingerbread keyboard
For those of you who need it, check THIS thread out!
n-Joie! (Enjoy)
R^7Z said:
For those of you who need it, check THIS thread out!
n-Joie! (Enjoy)
Click to expand...
Click to collapse
I've heard it doesn't work... Per another user, I have added a different recommendation:
arrrghhh said:
I noticed the (virtual) keyboard is comically tiny. Seems to work fine tho... If it does bother you, user "webxplore" said the app "gingerbread keyboard" (on the Market) fixes the issue. Thanks webxplore!
Click to expand...
Click to collapse
Gingerbread keyboard (market version)
Will see about getting the market version upped for those who are not able to access a wifi or have the awesome pull-out keyboard the RAPH/TP has
[R^7Z EDIT]Keep in mind, I have a RAPH110/TP/at&t Fuze
Free for all!
n-Joie! (Enjoy)
[/R^7Z EDIT]
Please note, we now have a source fix for the keyboard size and it will be integrated in the next testing image.
Not sure why WiFi works better in GB than FroYo but I just disabled and re-enabled like several times, without fail/error. I'm using the packaged build found in this thread and using Glemsom's kernel package for the 14th. If needed, I can supply screenshots.
R^7Z said:
Not sure why WiFi works better in GB than FroYo but I just disabled and re-enabled like several times, without fail/error. I'm using the packaged build found in this thread and using Glemsom's kernel package for the 14th. If needed, I can supply screenshots.
Click to expand...
Click to collapse
No need. I'll let stinebd know, I'm not sure what the difference would be... if he can backport something to Froyo, or if we are just going to be moving forward and focusing on GB. Thanks again for testing!
Thanks alot man this build is great! seems to boot and run faster and smoother then froyo ever did for me...only issues i ran into were not being able to see the calibration which if youtap on the screen it glitches and shows part of it.....but the main thing is i seem to have a problem staying connected to the internet and have to soft reset to get it working again....also airplane mode seems to get stuck once clicked and only a soft reset fixes it
m using this one is there anyway to chnge keyboard cx buttons are to small and my phone doesnot rotate any help
xtremists said:
m using this one is there anyway to chnge keyboard cx buttons are to small and my phone doesnot rotate any help
Click to expand...
Click to collapse
Read the second post. Gsensor doesn't work yet, but there's a fix in the pipeline. Keyboard fix as well, in the meantime... read the second post!!!!
Please read this entire post!
<<<This is a link to the... FAQ Click it!!>>>
I have created a complete bundle of GingerBread with the newest kernel from GIT (Feb 28 / 1276), and the newest rootfs from GIT (Feb 24).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps!
Directions:
1. Download the full bundle (zip). (Updated Mar. 11 2011)
If instead you just want the system.ext2 (zip) file (updated Mar. 25 2011) by itself... Don't download this unless you know you want to update!!
2. Extract it. You’ll see a folder, GBX0A, copy its contents to the root (base) of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Download the ts-calibration file from this post (should work for RHOD/TOPA) and extract the .zip to where you run haret.exe from - typically the root or 'base' folder of the SD card. Not within any folders, unless you run haret.exe from a folder!
**If you have issues with the above file, you must calibrate manually. To start manual calibration, just delete any ts-calibration files and boot. Sometimes this doesn't work, and you have to use an older kernel from GIT (I found 1225 works well) and generate the ts-calibration file by booting and pressing the 5 zones. Once you have a good calibration file hold on to it (make 15 copies if it's a really good one ), reboot & go back to the newest kernel from the autobuild service! Thanks**
6. Run haret.exe... Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins or so the media scanner can go thru everything, etc. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get newer or archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
In addition, I am using the newest rootfs from GIT - Feb. 10. There are other rootfs options, see F22’s thread if you want to use more keys or move around the home button. Of course, there's always the roofs autobuild service if you want "stock" rootfs images - F22 builds his off of these and modifies them .
See Incremental Updates for more information on this topic of updating!!
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data, Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Obviously this build is Alpha, and there are going to be problems. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
stinebd's original post HERE
Mar. 11 2011 Changelog
Things broken in this build:
libgps - explains itself, no GPS and probably no netloc (cell-tower based location). I think this also breaks the stock browser, I recommend using Dolphin Mini!
HW3D is either not working, or just not preset - I ran neocore and let's just say a lot of textures are missing. Got a ridiculous score, but again - no textures, not much to render haha.
Data - very flaky - CDMA users have data break for them after every phone call, and GSM users seem to have better luck but it's not flawless. Even seen reports of wifi having issues with data not going out to the WAN. There is a bug filed on this issue.
Anything that's broken in Froyo, is probably broken in this build. Although what is interesting, I noticed that in this build I don't have the landscape-on-boot issue that I get with Froyo...
Changelog March 25, 2011
Further tuned keyboard sizing to be useful on VGA (also made the key labels bigger)
World-phone settings support (very important for future RIL enhancements especially on CDMA)
Enabled HSPA icon (someone on GSM please let me know if it actually works)
Works good so far
Been using this for about 3 hours so far. Here's a little review. Upgraded through Stinebd's link in the XDAndroid thread (same as this I guess, but the arggggh's complete package includes all files needed). I deleted the data.img and replaced my system2 file. The first boot set itself up and then rebooted to winmo. The second boot worked. I was able to download Titanium backup from the market and restore my apps that I was using in Froyo. Overall it was working well. The default keyboard is tiny on my screen. My data connection is a little finicky as it was working when I restored my apps, but I could not connect after a while (same thing happened in my Froyo build periodically). As far as speed is good and bad, sometimes it's quick, other times it's quite slow. Overall, it's pretty good considering it was just released to us. Looking forward to future builds.
Edit: I reused my calibration file from Froyo. No issues
Rhod400, 2/10 Zimage and Rootfs from GIT
mmm, I may be blind but I can't see any download link! I'd like to test it and let you know!
anyway I already want to thank you for the hard work!
The system file was posted by stinebd in this thread:
http://forum.xda-developers.com/showthread.php?t=627997&page=1226
Thanks, I've included the original link to stinebd's post in my first post.
Still working out kinks, and stine will probably want me to host it on files.xdandroid.com - sorry for the delay... It will be here soon .
so this is the neopeek build only in an image?
husam666 said:
so this is the neopeek build only in an image?
Click to expand...
Click to collapse
This has nothing to do whatsoever with neopeek. This is AOSP code, modified to work on our phones. The system image work is done entirely by stinebd, and I have made a bundle - Link up!
arrrghhh any idea what the kernel incompatibility comes from? Thats strange...
edit- nvm I reread it a 5th time and understood heh
randomblame said:
arrrghhh any idea what the kernel incompatibility comes from? Thats strange...
Click to expand...
Click to collapse
You mean the calibration issue? Some commit broke it, not sure which one. There's rumors that we can read it from the spl, then we won't need a kernel-based calibration - we'll be able to do it in userland, which is really what we want especially going forward to NAND.
Gonna try this release this weekend
rhod100 does have the same panel problems as on a FRX04 release a guess?
JBS2 said:
Gonna try this release this weekend
rhod100 does have the same panel problems as on a FRX04 release a guess?
Click to expand...
Click to collapse
Panel problems are kernel related, not system image related.
What kernel do you run FRX04 on...? Thanks.
arrrghhh said:
Panel problems are kernel related, not system image related.
What kernel do you run FRX04 on...? Thanks.
Click to expand...
Click to collapse
Most recent from your testing topic.
Panel wakes up very slow normally or after touching the screen or power button multiple times.
JBS2 said:
Most recent from your testing topic.
Panel wakes up very slow normally or after touching the screen or power button multiple times.
Click to expand...
Click to collapse
Ah. Again, that's a testing kernel. Let's keep testing kernel discussion in that thread and build talk about this build in this thread... Thanks...
arrrghhh said:
Ah. Again, that's a testing kernel. Let's keep testing kernel discussion in that thread and build talk about this build in this thread... Thanks...
Click to expand...
Click to collapse
I know, you asked which kernel I was using
Just wondering if these release has something to do with the panel issues but I realize this is a kernel related problem.
Keep up the goog work, I'll keep testing the testing kernels to see if the known problem could be fixed
Okay, here's my 2cents:
BTW, i use rhod100.
Hardware3d doesn't work because the line is missing from the startup (as far as i am concerned, maybe you removed it on purpose).
steyn_e said:
Okay, here's my 2cents:
BTW, i use rhod100.
Hardware3d doesn't work because the line is missing from the startup (as far as i am concerned, maybe you removed it on purpose).
Click to expand...
Click to collapse
That entry is no longer required. Put it in and see... Thanks!
this is such an exciting build. It runs really fast. keep up the good work guys. Btw, to get a bigger gingerbread keyboard, search for "gingerbread Keyboard" in the market. its a larger sized version of the one that comes with the rom.
kdub94 said:
this is such an exciting build. It runs really fast. keep up the good work guys. Btw, to get a bigger gingerbread keyboard, search for "gingerbread Keyboard" in the market. its a larger sized version of the one that comes with the rom.
Click to expand...
Click to collapse
I've already included a fix in the second post, thanks!
Hey folks,
This is a completely new build, with all the new changes baked in. We wanted to do a semi-official test release to collect bugs and hopefully do a formal official release with everything settled. The main pain point is the CSV files (see pre-install prep).
So a brief overview:
New acoustic routing code baked in. Should fix most if not all audio routing problems, and will provide more debugging if stuff does go wrong. Also allows for more granular tweaking, see the CSV files.
GPS fixes for GB - GPS not only works in GB now, but it doesn't kill sleep! I was able to use GPS, get a solid lock, and put the device to sleep no problem.
BT should work & well with the new acoustic code. Post results.
RHOD users now have a choice of kernels. .35+ all have the new acoustic - so .35, .39, 3.0 and 3.1 are all fair game now... This is bundled with .27!!
Keep in mind, autobuild .27 kernels will produce no audio in this build... Obviously the bundled kernel will work, and the absolute newest .27 autobuild kernel does work now - Feb.27 2012 or newer.
rootfs tweaks - first, it will detect which kernel you're on (.27 or .35+) and automatically apply the correct firmware. Second, is it will always copy/extract the modules... failures there were getting annoying, and this is surefire if brute-force...
Few Easter egg apk's...
Probably a lot I'm forgetting, this might change
Pre-Install Prep REQUIRED!!!
This step is crucial, and I forgot all about it! You must copy all of the *.CSV file from your WinMo ROM - these are in the \Windows\ directory. There's a very easy way to do this. It involves the Total Commander app for WinMo (Direct Link for the perpetually lazy...) (included in EnergyROM and others probably).
Now you're in Total Commander looking at your \Windows\ directory. Whew... lots of files. Fear not! Hit the "CTRL" button, then the green "Plus" button. This opens the Select/Unselect files dialog. Put in *.csv, press "select" and voila. All CSV files are selected. Now - File -> Copy/Move -> I want you to copy these (should be 10) files to the ROOT of your SD card. No folders!!! This is hardset right now, until we get it all implemented into the build properly. Thanks!
Install
Assuming you've done the pre-install prep; this is installed just like the other XDAndroid builds - grab your startup.txt (don't forget rel_path= if you don't have it at the root of the SD!), ts-calibration and boot!
Download
Caveat List
CDMA users might get a crash in phone.apk and no service on boot. If waiting doesn't resolve the issue, then reboot. Should come up fine...
BT might still be flaky
The CSV files from my RHOD400 are attached for the lazy. I'd like to gather CSV's from each RHOD, I'm curious if any ROM devs have changed them out either... This could get interesting. If you folks don't mind, post up your CSV's, point out differences with mine, etc... We're trying to figure out how to unify these, if possible! Thanks!
Please post back any issues, enjoy!
GBX0C Changelog
Camcorder: Now works (tested on rhodium).
Acoustic: Bug-fix : correct random loss of dual(rear)-mic.
MMS: Bug-fix: Slides with zero duration on Sprint.
Gps: Bug-fix: Init/de-init sequence fix (correct gps not starting up after being unchecked in Settings).
Gps: Bug-fix: End gps session with a correct rpc call (relevant to amss6125 devices).
Gps: Bug-fix: Don't send delayed position requests after session has ended (possibly relevant to Navigation issues).
Gps: New feature: Xtra (aGPS) -> verified to work on rhodium/cdma raph.
X1 specific: Screen rotation patch.
Added tytung's GPS injector app to AndroidApps\Other as well as updating/cleaning up some apps in AndroidApps.
Modified rootfs for newest apsta firmware & wifi firmware - wifi tethering now works flawlessly in the newest kernels! .27 is still bundled for the record...
Just to get people going on some of the newer kernels.
2.6.35 is currently auto-built at:
https://code.google.com/p/zimages/downloads/list
Emwe has been maintaining this tree, and he is most qualified to speak about it, but pretty much everything is functional barring camera.
Head over to this testing thread for more information on 2.6.39/3.0/3.1 kernels for Rhodium.
arrrghhh said:
Pre-Install Prep REQUIRED!!!
This step is crucial, and I forgot all about it! You must copy all of the *.CSV file from your WinMo ROM - these are in the \Windows\ directory. There's a very easy way to do this. It involves the Total Commander app for WinMo (included in EnergyROM and others probably).
Now you're in Total Commander looking at your \Windows\ directory. Whew... lots of files. Fear not! Hit the "CTRL" button, then the green "Plus" button. This opens the Select/Unselect files dialog. Put in *.csv, press "select" and voila. All CSV files are selected. Now - File -> Copy/Move -> I want you to copy these (should be 10) files to the ROOT of your SD card. No folders!!! This is hardset right now, until we get it all implemented into the build properly. Thanks!
Download
Click to expand...
Click to collapse
You probably saw this problem coming but I have just the stock windows rom, how would i go about doing this? (or do i have to go and find each and every CSV file )
I googled and downloaded total commander on my laptop, and i got it to show my phone, but it only shows up with my SD card stuff, not my phone itself (unless thats whats supposed to happen )
Will keep trying! -determined-
A cool username said:
You probably saw this problem coming but I have just the stock windows rom, how would i go about doing this? (or do i have to go and find each and every CSV file )
I googled and downloaded total commander on my laptop, and i got it to show my phone, but it only shows up with my SD card stuff, not my phone itself (unless thats whats supposed to happen )
Will keep trying! -determined-
Click to expand...
Click to collapse
Sigh, are you freakin serious? I even link to Total Commander's website in my instructions.... Not sure how much easier I could've made it.
I also just attached the CSV's for the lazy... .
It does say TESTING in the title, no? Yea. It does..
Hehehe I know, I know, i guess i just don't have very much knowledge with this kinda stuff (obviously) Thanks!
A cool username said:
Hehehe I know, I know, i guess i just don't have very much knowledge with this kinda stuff (obviously) Thanks!
Click to expand...
Click to collapse
Testing/development threads usually mean "please pitch in and help test if you can. If not, please wait until the final stable release".
Make sense?
Okay, i'll be glad to help test it if someone could post the CSV files for a rhod300 (if its not too much trouble). If not, I will wait for the stable release. Thanks arrrghhh!
Yes, makes sense
Installed the rom but i've got a problem with the fact that the screen dissapaers after about 5 seconds, so i can't even put in my pin.
also i'll put in the csv files from my rhodium100.
Edit: Works good on second boot, had to change the calibration file and it's works good and fast. Only thing i have is that i now have got 919 contacts instead of the (normal) 135.
A lot of text messages for tonight
Edit 2:when i make a phone call i get a black screen and the phone crashes after that.
Camera works when you don't move a lot, otherwise it's blocked.
bleutooth doesn't work for me it connects to my parrot but i can't make a phone call.
Schumi_wk said:
Edit 2:when i make a phone call i get a black screen and the phone crashes after that.
Camera works when you don't move a lot, otherwise it's blocked.
bleutooth doesn't work for me it connects to my parrot but i can't make a phone call.
Click to expand...
Click to collapse
Sounds like a proximity sensor issue - not sure if some of the GSM rhod proximity related adjustments made it into the acoustic .27 kernel. You should try one of the newer kernels (not sure what's the status with .35 and GSM-proximity, but on 39+ I expect you won't have this issue).
This GB build, and these new kernels are kexec enabled. Meaning if you are on .35 or newer, and would like to interchange the kernel on-the-go, without re-booting to WinMo you can do the following:
1. While in Android, copy the new kernel and modules to the same location (over-writing the zImage) as your current kernel (adb push).
2. Go to the shutdown menu in GB, and select "Kexec".
3. Phone will reboot within Android, using the new kernel.
Again, this feature only works with the new kernels.
---------- Post added at 06:20 PM ---------- Previous post was at 05:38 PM ----------
Schumi_wk said:
Edit 2:when i make a phone call i get a black screen and the phone crashes after that.
Click to expand...
Click to collapse
Let me know if you are willing to test a prox support for rhod 100. I'll pm you a kernel pack.
Just tried the .39 kernel and bluetooth didn't work with that one. The phone did work with this one.
Than did the 3.0 kernel and bluetooth works but there i don't have wifi.
The 3.1 kernel doesn't load it stops at
3.711395 mmcblk0:mmc1:1234 SA0BG 7.42gb
3.728118 mmcblk0: p1
Than did the .35 kernel and bluetooth worked but no wifi.
No more testing for me today, i'm getting ready for the last hours of 2011.
For all of you enjoy the last moments of 2011 and start 2012 with a lot of fun!!
Schumi_wk said:
Just tried the .39 kernel and bluetooth didn't work with that one. Than did the 3.0 kernel and bluetooth works but there i don't have wifi. The 3.1 kernel doesn't load it stops at 3.711395 mmcblk0:mmc1:1234 SA0BG 7.42gb
3.728118 mmcblk0: p1
Than did the .35 kernel and bluetooth worked but no wifi.
No more testing for me today, i'm getting ready for the last hours of 2011.
For all of you enjoy the last moments of 2011 and start 2012 with a lot of fun!!
Click to expand...
Click to collapse
You must understand that BT is only functional in 3.0 and .35 (well, and .27). I don't know about the state of wifi in any of 'em... Should work in .39, I thought it worked in .35 as well. Haven't booted .35 in quite some time myself. Logs are really going to be necessary to triage any of your problems tho. Thanks, enjoy New Years.
arrrghhh said:
Caveat List
The CSV files from my RHOD400 are attached for the lazy. I'd like to gather CSV's from each RHOD, I'm curious if any ROM devs have changed them out either... This could get interesting. If you folks don't mind, post up your CSV's, point out differences with mine, etc... We're trying to figure out how to unify these, if possible! Thanks!
Please post back any issues, enjoy!
Click to expand...
Click to collapse
Here are my .csv files for the Tilt2 (Rhod300). Have not compared to the RHOD400 yet.
Here's my CSV files from my RHOD500
BTW, I can't use the Wi-Fi
I'm using the default kernel and settings that came in the bundle...I will try using a new data.img
Logcat says: "E/WifiService< 1328>: Failed to load Wi-Fi driver."
nickleby said:
Here's my CSV files from my RHOD500
BTW, I can't use the Wi-Fi
I'm using the default kernel and settings that came in the bundle...I will try using a new data.img
Logcat says: "E/WifiService< 1328>: Failed to load Wi-Fi driver."
Click to expand...
Click to collapse
You didn't start on a new data.img...?
This makes me think the modules didn't copy, but I force them to every time. Perhaps I should rm them all first... bleh.
You're not mixing and matching anything are you...?
arrrghhh said:
You didn't start on a new data.img...?
This makes me think the modules didn't copy, but I force them to every time. Perhaps I should rm them all first... bleh.
You're not mixing and matching anything are you...?
Click to expand...
Click to collapse
I'm using a new data.img, but the wifi still not work...I'm using the rootfs, zimage, kernel, initrd, startup.txt and system.ext2 that came in the bundle, I just added my ts-calibration
nickleby said:
I'm using a new data.img, but the wifi still not work...I'm using the rootfs, zimage, kernel, initrd, startup.txt and system.ext2 that came in the bundle, I just added my ts-calibration
Click to expand...
Click to collapse
Hrm. Can you pull some logs? I tested wifi every which way and it was always working. I did make some rootfs tweaks, so I guess it's possible it's using the wrong firmware...?
Someone had a wifi issue, rebooted and it went away. I hate wifi .
Yay! Merry Christmas and Happy New Year guys. Can't wait to try this and get back on .39. And sort-of hot-swapping kernels? Sweet.
arrrghhh said:
Hrm. Can you pull some logs? I tested wifi every which way and it was always working. I did make some rootfs tweaks, so I guess it's possible it's using the wrong firmware...?
Someone had a wifi issue, rebooted and it went away. I hate wifi .
Click to expand...
Click to collapse
I rebooted the phone, but it doesn't work...Here's a logcat, if you need another type of logs, please tell me...
nickleby said:
I rebooted the phone, but it doesn't work...Here's a logcat, if you need another type of logs, please tell me...
Click to expand...
Click to collapse
I just see a lot of this
E/WifiService( 1320): Failed to load Wi-Fi driver.
So uh... I think that indicates a modules mismatch? rm -rf /lib/modules and rebootski. I guess I need to make that change in init... copying and extracting every time doesn't work.