Here are the nbh files compiled upto the last change in the Dzo's GIT on the 03-05-10.
15-04-10 Updated - Uploaded new nbh's due to not working with Sense 2.1 build. Thanks kallt_kaffe & toasty_.
22-04-10 Updated - Latest Change from Dzo's git - Fix GPS enable/disable race condition on Kaiser.
26-04-10 Updated - Latest Change from Dzo's git - Add delays to vfe commands
29-04-10 Updated - Latest Change from Dzo's git - Add a delay to the adsp code and change the dsp irq handler.
03-05-10 Updated - Latest Change from Dzo's git - Add adsp delay and irq trigger change for cdma devices only.
PS: You may have to wipe system to get this to work so if your currently happy wait until you update your andriod system.
Here's the ones for the AT&T Tilt.
Updated 03-05-10 - See Post 1
What's the difference between the files in the first post compared to the second post?
Dukenukemx said:
What's the difference between the files in the first post compared to the second post?
Click to expand...
Click to collapse
ATT Tilt Keyboard layout.
tried this with eclair, and it gets stuck on at
Code:
A N D R O I D
xPreSiDenT said:
tried this with eclair, and it gets stuck on at
Code:
A N D R O I D
Click to expand...
Click to collapse
What build of eclair did you use as it sounds like the kernel is booting as it get's to where ANDRIOD is displayed.
I'm been using polymod 2.1g + the upgrade posted in the thread, it's been working ok for me. My knowledge of Andriod and linux is still quite limited, so I'm not sure what else to recommend.
happened to me too... just reinstalled the system with androidinstall.tgz (without wiping data) and all went well
I'm also using 2.1g, but I dont know about the update. Ive installed all the updates (polymod_2.1g-BT_Update.zip and the full market update) posted after 2.1g.. are there any more? I dont know how to update the kernel as is posted on the first page:
UPDATE 19 Mar 2010:
Latest .NBHs and Kernel for Kaiser & Polaris posted to http://ponack.net/poly/BT_Update/ , thanks again to Mr PaveL for building them.
If you're using HaRET, the same zImage now works for Donut AND Eclair. For Eclair you will need to add hw3d.version=1 to the command line in your default.txt . If the previous BT zImage wasn't working for you, this one should. (New Vogue .nbh and the same kernel can be found @ dzo's site.)
Click to expand...
Click to collapse
as far as I know the zImages are for haret users only... am I wrong?
xPreSiDenT said:
I'm also using 2.1g, but I dont know about the update. Ive installed all the updates (polymod_2.1g-BT_Update.zip and the full market update) posted after 2.1g.. are there any more? I dont know how to update the kernel as is posted on the first page:
as far as I know the zImages are for haret users only... am I wrong?
Click to expand...
Click to collapse
ZImages are for Haret you are correct.
PolyMod Update
http://forum.xda-developers.com/showpost.php?p=6105602&postcount=3011
What's the difference between the different Panel types? How do I know which one to use?
OshiHidra said:
What's the difference between the different Panel types? How do I know which one to use?
Click to expand...
Click to collapse
board-htckaiser.panel_type
Panel type used to power the panel off and on (see also vertical line issue)
[edit] Values
* 0 - Don't power off the panel
* 1 - Sony
* 2 - Topoly
* 3 - Topoly
Shamefully copied from here.
I just tried all three and settled on the one I think worked the best.
fultotop said:
ZImages are for Haret you are correct.
PolyMod Update
http://forum.xda-developers.com/showpost.php?p=6105602&postcount=3011
Click to expand...
Click to collapse
thanks alot! Am gonna try it right away. I seriously hope it solves my wifi issue :S
fultotop said:
Here are the nbh files compiled upto the last change in the Dzo's GIT 4 Days ago Fix kaiser usb (same as polaris). These are the first time I've done this, but I've tested them on my Kaiser.
Click to expand...
Click to collapse
Just a heads up. I also make my own NBH's and I noticed today another thing in tinboot.S that aren't up-to-date with the NBH's that DZO compiles.
Use a hexeditor and you will see that the mtdparts parameters are different. I've updated my NBH build (another thread here) and the noticable difference is that the partition sizes are different so that the system partition is larger than before. The data is still the same though.
I'm currently testing the Sense 2.1 build and it requires a larger system, that's why I noticed the difference.
Ok got the same problem with the nbh from DZO and yours. Problem is DZO uses other sizes and adresses for mtd-partitions, so if you are using Data and/or System on Nand, data can' be found.
Code:
DZO's NBH from 8th April:
mtdparts=msm_nand:[email protected](nand)ro,[email protected](root),[email protected](system),[email protected](userdata)
Yours:
mtdparts=msm_nand:[email protected](boot),[email protected](root),[email protected](system),[email protected](userdata)
maybe it works if you first flash nbh and then reinstall system and data
EDIT: OK, was allready said - I've been to slow
kallt_kaffe said:
Just a heads up. I also make my own NBH's and I noticed today another thing in tinboot.S that aren't up-to-date with the NBH's that DZO compiles.
Use a hexeditor and you will see that the mtdparts parameters are different. I've updated my NBH build (another thread here) and the noticable difference is that the partition sizes are different so that the system partition is larger than before. The data is still the same though.
I'm currently testing the Sense 2.1 build and it requires a larger system, that's why I noticed the difference.
Click to expand...
Click to collapse
Thanks that would explain why it wouldn't boot without reinstalling the system partition for some people.
toasty_ said:
Ok got the same problem with the nbh from DZO and yours. Problem is DZO uses other sizes and adresses for mtd-partitions, so if you are using Data and/or System on Nand, data can' be found.
Code:
DZO's NBH from 8th April:
mtdparts=msm_nand:[email protected](nand)ro,[email protected](root),[email protected](system),[email protected](userdata)
Yours:
mtdparts=msm_nand:[email protected](boot),[email protected](root),[email protected](system),[email protected](userdata)
maybe it works if you first flash nbh and then reinstall system and data
EDIT: OK, was allready said - I've been to slow
Click to expand...
Click to collapse
Thanks you saved me some time, I've updated them see first post.
FYI, all the links in the first two posts are dead.
EDIT: nevermind, evidently I'm having a serious problem with my browser right now. Links are fine.
You say these work with the Sense 2.1 build but that requires HVGA while according to the file names these are QVGA. Are these actually HVGA (480) but just have the wrong names?
Nevermind, tested it out myself and they really are 320 builds. Well, nothing a little hex editing couldn't fix...
OshiHidra said:
What's the difference between the different Panel types? How do I know which one to use?
Click to expand...
Click to collapse
320 works best with TyTn II. now you have to choose panel 1, 2 or 3. i suggest you try 2 or 3 because panel 1 have some pixel errors.
byron0318 said:
320 works best with TyTn II. now you have to choose panel 1, 2 or 3. i suggest you try 2 or 3 because panel 1 have some pixel errors.
Click to expand...
Click to collapse
Yes. Yes it does.
byron0318 said:
320 works best with TyTn II. now you have to choose panel 1, 2 or 3. i suggest you try 2 or 3 because panel 1 have some pixel errors.
Click to expand...
Click to collapse
On your TyTn II perhaps panel 2 or 3 work best, however all 3 panel types are used on most models of kaiser, depending on supply at the time of manufacture, so there is no really easy way to tell which panel type you have, apart from disassembling your kaiser and checking the part numbers on the lcd panel itself.
I have 2 almost identical kaisers (KAIS130) both are identical in every way, apart from the lcd panel, one has type 1, the other type 2.
Pixel errors, colour problems, lines and streaks on the display, are all symptoms of choosing the wrong panel type for your device, and the only thing you can do is use a different nbh, or change panel type in default.txt until you find the correct one.
Related
CyanogenMod 6 Kaiser [RLS5.2] - RC2 based, odex:ed build [6.8.2010]
This release is based on CyanogenMod 6 RC2, modified to be Kaiser & Polaris friendly (and hopefully Vogue too). Parts of other releases, mostly dzo's Fresh Froyo are also used.
What's new:
RLS5.1:
- Completely re-done release, based on CyanogenMod 6 RC2 FRF91
- System completely odex:ed (thanks kallt_kaffe for all your help with this)
- Google Apps FRF91 MDPI
- Wifi tethering - courtesy of urban69 and kallt_kaffe.
- Removed most of the "bonus" apps except Astro File Manager, due to /system size limit. To get YR Weather Widget, Brut Maps, Linpack or Nexusrevamped Live Walpaper dowload the AppPack.zip here, unzip the files to your SD card and install via Astro..
- Experimental libhtcgeneric-ril.so to enable 2G/3G switching (again all credits to kallt_kaffe) included. The enable/disable "2G mode only" switch in settings now works!!
For best performance enable compcache in Settings > CyanogenMod Settings > Performance. If you want to squeeze even more out of it disable dithering, also in Settings > CyanogenMod Settings > Performance.
Download RLS5.1: Mediafire, FileFactory or Megaupload!
Update RLS5.2
-New version of experimental libhtcgeneric-ril.so to enable 2G/3G switching (again all credits to kallt_kaffe) included
RLS5 and RLS5.1 can be updated to RLS5.2 via update attached below: rls5_rls5-2_update.zip.
What works:
Everything should be working as in other Froyo builds. But I may have missed someting - if so, please report!
- Phone: calls, SMS, standard stuff..
- Camera
- BT & BT audio
- Wifi
- Email
- MMS
- Exchange sync, Google sync
- Market
- GPS & Wireless (WiFi or Data) location
- JIT
- Compacache
- et cetera..
Installation:
Put the androidinstall.tar to /andboot folder and install to SD / NAND. SD users will find complete SD HaRET distro attached below, with zImage-froyo-26-07-10 (HaRET.zip). Edit default.txt according to your needs and wishes, but it should be o.k. for most Kaiser users (except panel and battery parameters - fix those). Polaris users should edit default-polaris.txt for Polaris. Vogue users need to use their standard default.txt.
I've tested RC5 on SD (ext2/ext2) install, so I really don't know how it will work on NAND.
If you have problems with Wifi connections, you can try other power levels using script made by kallt_kaffe:
Code:
$ sudo
# wifi_level.sh low|medium|high
To switch between Froyo | Eclair | Paid Market, use a script market.sh, made by kallt_kaffe:
Code:
$ su
# market.sh eclair|froyo|paid
There is a small DeskClock.apk issue in RLS5.X. To get back DeskClock.apk from RLS4, which is o.k. for our resolution, apply attached DeskClock_fix.zip.
Screenshots:
Check them out at CyanogenMod 6 screens page.
Credits go to:
- mssmision for porting CyanogenMod 6 for our devices and all the other work his done
- dzo for his kernels and Froyo releases - without you man there would be no Vogue/Kaiser Android community
- kallt_kaffe for many many contributions he made to Android Vogue/Kaiser community
- Incubus26Jc also for his fine builds and many contributions made to Android Vogue/Kaiser community
- Brut.all for his Maps mod
- DmK75 for the default.txt for Polaris and all the other contributions his done in testing and delivering fixes for this build. Thx man!
- Complete Vogue/Kaiser community
Thank you guys for your great work and sorry for stealing your ideas and soultions, but they're just to tempting not to be used and abused.
I'd be glad to get as much of your feedback as possible. Enjoy!
============================================================
History
RLS4:
- Fixed bootanimation to comply with 240x320 res, also slimmed down bootanimation.zip by 1 Mb
- Replaced all Google Apps with the FRF91-mdpi version
- Updated ADW Launcher to latest version 1.0.1-mdpi
- Removed LinPack
- Included updates from RLS3 in the main build
- Other smaller modifications and optimizations
RLS3:
- Replaced old Vending.apk with a new one from FRF91 source to fix constant FC'ing
- Replaced some other system resources with FRF91 source
- Updated ADW Launcher to latest version 1.0.1
- PNG'optimized and zippaligned all apk's - shaved ~ 10-15% off in average
- Optimized all OGG files - shaved 20-30% off in average (you shouldn't, but if you notice any drop in ringtones quality, please inform me)
- Included Brut Maps, Astro, NexusRevamped LiveWalpaper and LinPack in the release, on the account of newly freed space
- New kernel zImage-froyo-26-07-10 added to HaRET.zip
- Included Wifi tethering fixes made by kallt_kaffe (thx man, great work). No more post installations scripts needed to make it work.
Nice work! Sometime I will try this build.
Just about the best i've tried yet.
This is by far the most responsive version i've tried yet and i've spent about two days trying all the versions mentioned in the
"Android Build Index - Look here before asking" -I can't post the link-
I'm trying this on NAND. I can't get Wifi to work on my kaiser but i'm going to keep playing around with this one.
Love the speed.
Oh, what is the name of the female football picture/wallpaper?
Hi,
I will try it on my Pola.
This build is useful for using bluetooth speakerphone in car?
Chick wallpaper.
http://bit.ly/acABBj
wifi won't start. It just states "error"
@nemuro are you a Kaiser or Polaris user and did you apply my update?
Best yet!!
I'm not sure how, but Wifi is now working. It may have something to do with fixing permisions between a re-install. This version is quick and snappy. My favourite so far!!!
milanche said:
If you find any problems, please report..
Click to expand...
Click to collapse
Where i install update, i seen message "tar: short read"
Is error?
DmK75 said:
Where i install update, i seen message "tar: short read"
Is error?
Click to expand...
Click to collapse
No. It installed fine, don't worry! I get that error too, it has something to do with the way 7Zip I use makes tarballs, but it has no effect on install.
milanche said:
@nemuro are you a Kaiser or Polaris user and did you apply my update?
Click to expand...
Click to collapse
Yes, I applied the update. I am using kaiser, and haret + latest z-image. Is it the problem that I am using a wrong version of default.txt? Do you want me to post that file?
Gonna try it tonight...
Ive been using urban69's rom for 5 days and have enjoyed it although am having application fc's frequently and still dealing with the battery issues....I'll try this on Nand tonight and reply back....Thanks for all your work!!!
If it weren't for all of you dev's we'd be in tech limbo!!!
First of all...Im new to installing Android on Kaiser, so sorry for stupid q's and stuff...
Ive installed it on a danish Tytn II, it works, with some errors...
1. Wifi doesnt work(dont know why...just doesnt find any networks(and it seems to have no macaddress, at least thats what the infobox says, the same about bluetooth)
2. No marked...Weird i think
3. Battery stuck at 15%
4. i sometimes have problems answering calls...
Think that was it for now...Else its a great build...Thx a lot..
THink i will install another build for now...but will probably try it again...
milanche said:
No. It installed fine, don't worry! I get that error too, it has something to do with the way 7Zip I use makes tarballs, but it has no effect on install.
Click to expand...
Click to collapse
Thank for this build!
I install it on my Polaris and tested: Wifi, BT and GPS works.
Also i noticed full russian translate and working superuser app!
One issue in Market, it sometimes "stopped unexpectedly".
nemuro said:
Yes, I applied the update. I am using kaiser, and haret + latest z-image. Is it the problem that I am using a wrong version of default.txt? Do you want me to post that file?
Click to expand...
Click to collapse
Please try my latest release where all needed HaRET files are included. And don't forget to change panel type in default.txt to correspond your panel!
Zalasta said:
First of all...Im new to installing Android on Kaiser, so sorry for stupid q's and stuff...
Ive installed it on a danish Tytn II, it works, with some errors...
1. Wifi doesnt work(dont know why...just doesnt find any networks(and it seems to have no macaddress, at least thats what the infobox says, the same about bluetooth)
2. No marked...Weird i think
3. Battery stuck at 15%
4. i sometimes have problems answering calls...
Think that was it for now...Else its a great build...Thx a lot..
THink i will install another build for now...but will probably try it again...
Click to expand...
Click to collapse
That's weird. I have Wifi and BT working. Please download the new full SD HaRET release from first post and see how this one works for you. It has all needed files included, including latest 15-7 kernel.
Added new complete androidinstall.tar release to first post!
doesn't work on nand, it's too fat to be installed in nand... the update fails with no space left on device as does the new androidinstall
i guess something needs to be took off to install in nand
milanche said:
If someone is kind enough to send me default.txt for Polaris, I'll be glad to include it!
Click to expand...
Click to collapse
Here default.txt for Polaris, i use it.
DmK75 said:
One issue in Market, it sometimes "stopped unexpectedly".
Click to expand...
Click to collapse
Yes, I have the same problem. Will look into it.
DmK75 said:
Here default.txt for Polaris, i use it.
Click to expand...
Click to collapse
Thank you very much! Will include it into next release.
succo said:
doesn't work on nand, it's too fat to be installed in nand... the update fails with no space left on device as does the new androidinstall
i guess something needs to be took off to install in nand
Click to expand...
Click to collapse
Ok, thanx. I'll look into it.
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!
CyanongenMod 6.1
Download CyanogenMod 6.1 Touchwiz-Port (Android 2.2)
Based on CyanongenMod 6.1 for Xperia X1. Tanks @ squallvia
Original Source: http://forum.xda-developers.com/showthread.php?t=1030695
- working: Wifi, GPS, 2G/3G data, Sound, Market, etc.
- camera and fm radio did not work
known Bugs:
keyboard mapping:
change physkeyboard=rhod100_uk in startup.txt
rhod100_uk
rhod100_de
rhod100_it
rhod110
rhod210
tilt2
rhod400
rhod500
Installation:
First format your sd card with min. 2 parititions. (1x fat32, 1x ext2) Video: http://www.youtube.com/watch?v=oyO6DOS1leQ&feature=player_embedded
Read this: http://forum.xda-developers.com/showthread.php?t=1021658
- copy files to sd card (fat32-partion)
- copy attached startup.txt to /sdcard/nkpinstall
- run from windows mobile /sdcard/nkpinstall/install.exe (phone will reboot after finishing installation)
- run now, /sdcard/haret.exe
For CyanogenMod 7 use this link: http://forum.xda-developers.com/showthread.php?t=1008139
Maybe someone can help fix missing camera?
attached files = this files are different to original source
Thanks )
Hey thanks, tried this on my Rhod210 and it's very fast. Been running it all day today and it hasn't given me any major problems. I replaced the Kernal with the latest Wistilt2 one because I was having issues with my phone's screen waking up.
Keep up the good work!
Nice!! Its so happens that I'm getting an Xperia X10 in a couple days as well! Moving from my beloved Tilt2
But on the other hand... I'm getting a freaking Android device!!!
I'll be better able to support Rhodium now though since I will have both devices and will be able to port freely between the two
keymapping fixed:
change physkeyboard=kovsq in startup.txt
rhod100_uk
rhod100_de
rhod100_it
rhod110
rhod210
tilt2
rhod400
rhod500
For your interest:
Those builds above are forked or based or contain parts of my old ROMs.
An almost full working CM7.1 will be released later today to Team Members for testing on several devices. I am doing all my internal test on Rhod300 / Tilt2 and everything looks nice. So stay tuned it should be also available very soon to public.
So who's excited about magldr
Sent from my T-Mobile myTouch 3G using Tapatalk
dswaggz said:
So who's excited about magldr
Click to expand...
Click to collapse
Please, keep the useless off-topic comments to yourself.
To the OP, I've already posted a version of CM7 from Neopeek..
http://forum.xda-developers.com/showthread.php?t=1008139
I'll keep updating it as well. If this is for the Xperia X1, don't you think it belongs in that section of the forum?
Keep the CM6 build tho - I'd like to see one optimized for the RHOD, if possible...
As the annoying crashes with GAPPS have now been solved I will also pick up the CM6.1.X and recompile it after CM7 is out
arrrghhh said:
To the OP, I've already posted a version of CM7 from Neopeek..
http://forum.xda-developers.com/showthread.php?t=1008139
I'll keep updating it as well. If this is for the Xperia X1, don't you think it belongs in that section of the forum?
Keep the CM6 build tho - I'd like to see one optimized for the RHOD, if possible...
Click to expand...
Click to collapse
i will keep the touchwiz cm6.1 build. only camera and fm radion did not work. maybe someone can help to get camera working.
Hi i can not install the Rom´s with this kind of installation instructions.
can we get a detailed installing instruction please?
I tryd it several times, i don't know where i have to place the attached files...every time when i want to start via haret.exe the installer starts up and rebboting after the procedure aaahhhhhhhh
Pleas help
schlei said:
Hi i can not install the Rom´s with this kind of installation instructions.
can we get a detailed installing instruction please?
I tryd it several times, i don't know where i have to place the attached files...every time when i want to start via haret.exe the installer starts up and rebboting after the procedure aaahhhhhhhh
Pleas help
Click to expand...
Click to collapse
Check out this tutorial: http://forum.xda-developers.com/showthread.php?t=1021658
WoW my Rhodium100_de was never so fast in Android !!
Really nice im running the Cyanogen 6.1 Touchwiz with an 8gb class4 card impressive Speed !
Thx so much this is the way !
Can anyone tell me why my orientation is out of wack? the phone's orientation is either showing upside down or facing away from the keyboard when in landscape mode??
scattaman said:
Can anyone tell me why my orientation is out of wack? the phone's orientation is either showing upside down or facing away from the keyboard when in landscape mode??
Click to expand...
Click to collapse
Just turn off the auto orientation switch, this will fix the problem for now until a fix is released.
scattaman said:
Can anyone tell me why my orientation is out of wack? the phone's orientation is either showing upside down or facing away from the keyboard when in landscape mode??
Click to expand...
Click to collapse
The startup.txt file in the first post fixes the orientation.
New Download.
Changes:
- replaced startup.txt files
- replaced zimage and modules (rhodium - from last xandroid build)
- added ts-calibration file
walter79 said:
New Download.
Changes:
- replaced startup.txt files
- replaced zimage and modules (rhodium - from last xandroid build)
- added ts-calibration file
Click to expand...
Click to collapse
Thanks Man. I just tried the build out and it is awesome! I do recommend the 4/15 testing kernal with it. I appreciate your efforts with this. Looking forward to a stable CM7
vnes1984 said:
Thanks Man. I just tried the build out and it is awesome! I do recommend the 4/15 testing kernal with it. I appreciate your efforts with this. Looking forward to a stable CM7
Click to expand...
Click to collapse
You can use all new kernel. Only replace zimage and module file.
I do some test with clockworkmod.
Easy way for updates.
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.