Since data drops on PPP builds still appear to be a major problem for some users, I decided to post this workaround for converting any sense PPP build to RMNET. I have only tested this on Mdeejay Revolution build but should work with any sense build. I have used this for more than 10 days now without any problems whatsoever: everything worked like on the original build.And no data drops.
All attached files were extracted from Sergio's CoreDroid version 0.5 which is an RMNET build. Hope he doesn't mind.I am not at all a developer
The steps are outlined below:
1. Download and extract the attached files on your PC
2. Open the Android folder of your build on your PC, and copy + replace the zImage and rootfs with the extracted ones.
3. Boot into Winmo and transfer your android folder to your SD card; also transfer the extracted module folder to your SD
4. Boot into Android; after initial setup, reboot again.I recommend a clean fresh install (ie without any old data image; you may re-use your data.img after setup is complete)
5. Use Root explorer to copy and replace the 2 files in the extracted modules folder into \system\lib\modules.
6. Reboot and enjoy
UPDATE 7/11/2010
[08/11/2010]After further testing of this update, I have found the screen to be laggy and had a SOD. I tried reinstalling after that and had no data connection but wifi worked ok. I have therefore abandoned using the update and sticking with the original one above. Of course if it works for you stick with it.
I have tested a newer nexus kernel of 5/11/2010 (found here) on Mdeejays Desire Revolution build (Desire based build). Both wifi and data work, and camera is 5MP. However only a clean fresh install appears to work.
Just download the file NewRMNET, extract contents unto desktop, copy all 3 into the Android folder of your build. Then boot into Winmo and transfer to SD card. Boot into android 2-3 times. That's it.
Once again the rootfs.img file is from Coredroid v0.5
Please leave feedback. I dont use BT or wifi Hotspot so will not know if they work.
Cheers.
Hmmmm... I think I'll try this as soon as I get home. Will edit this post with an update in a few hours.
EDIT:: Seems this actually broke my ROM all together.. Sucks... Oh well. I've been meaning to test a few other ROM's out anyway. This just gives me a good excuse to finally do it.
I'm downloading now....gonna try it and see.i'll let you know how it does!!Thanks
Hi,
Thank you for sharing.
So does that mean that for Sergio's CoreDroid version 0.6 ROM ... it already has RMNET right?
CoreDroid 0.5 is RMNET, 0.6 is PPP.
tried it and it didn't help any.and now my wifi doesn't work,just gettin an error message.going back to the way I had it before!
Yz450rider14 said:
tried it and it didn't help any.and now my wifi doesn't work,just gettin an error message.going back to the way I had it before!
Click to expand...
Click to collapse
Wifi will not work if the bcm4329.ko and tun.ko files contained in the modules folder are not replaced in \system\lib\modules folder with root explorer or a file explorer with root rights.
Yz450rider14 said:
tried it and it didn't help any.and now my wifi doesn't work,just gettin an error message.going back to the way I had it before!
Click to expand...
Click to collapse
Was that an internet temper tantrum?
Seems to work well.. so far no problems and data is slow but steady.. Better than constant connection loss.. I created a folder set> 'root/system/lib/modules' in my android folder to make wifi work perfectly...No need to use root explorer. and if I switch zimage again, its easy to delete.. Thanks!
stonesolouk said:
Since data drops on PPP builds still appear to be a major problem for some users, I decided to post this workaround for converting any sense PPP build to RMNET. I have only tested this on Mdeejay Revolution build but should work with any sense build. I have used this for more than 10 days now without any problems whatsoever: everything worked like on the original build.And no data drops.
All attached files were extracted from Sergio's CoreDroid version 0.5 which is an RMNET build. Hope he doesn't mind.I am not at all a developer
The steps are outlined below:
1. Download and extract the attached files on your PC
2. Open the Android folder of your build on your PC, and copy + replace the zImage and rootfs with the extracted ones.
3. Boot into Winmo and transfer your android folder to your SD card; also transfer the extracted module folder to your SD
4. Boot into Android; after initial setup, reboot again.I recommend a clean fresh install (ie without any old data image; you may re-use your data.img after setup is complete)
5. Use Root explorer to copy and replace the 2 files in the extracted modules folder into \system\lib\modules.
6. Reboot and enjoy
Click to expand...
Click to collapse
This work around is a great idea, however changing the zImage file is changing the kernel. I believe coredroid v.05 uses mychiprimas r11 kernel to be rmnet. the internet is great but then there is low incall volume as well as low notification and ringtone volume. Those are a downer for me.
I read somewhere that Hastarin was making a RMNET kernel to try out but I dont know how that turned out.
Try this low volume fix here; worked great for me.
R3BrotherJr said:
This work around is a great idea, however changing the zImage file is changing the kernel. I believe coredroid v.05 uses mychiprimas r11 kernel to be rmnet. the internet is great but then there is low incall volume as well as low notification and ringtone volume. Those are a downer for me.
I read somewhere that Hastarin was making a RMNET kernel to try out but I dont know how that turned out.
Click to expand...
Click to collapse
awesome!!
stonesolouk said:
Try this low volume fix here; worked great for me.
Click to expand...
Click to collapse
thank you so much for the sound fix, does anyone know if bluetooth is working normally with the RMNET workaround?? I mean a2dp and FF, RW, play/pause, as well as in call??
can someone comfirm??
THANK YOU SOOOOOO MUCH!!! Sick and tired of PPP failing!!!! Again many thanks.
R3BrotherJr said:
I read somewhere that Hastarin was making a RMNET kernel to try out but I dont know how that turned out.
Click to expand...
Click to collapse
I did it, but turns out RMNET in the EVO tree is broken.
I'm not sure what the OP has done here. I would presume he's provided a Nexus based kernel and files to convert a particular build to RMNET.
If so that's a step backwards in my opinion. PPP with the recent patches to the kernel and wrapper is about as stable as we could hope for and we have a lot of fixes since the Nexus tree was last updated.
PPP still has to reconnect if your phone hops between towers/bands but seems to do so relatively reliably now. I have no idea how RMNET handles that situation.
Of course I realize others out there may want to live with RMNET and without the other fixes/features (working compass, g-sensor fixes, light sensor, etc). Each to their own.
stonesolouk said:
Since data drops on PPP builds still appear to be a major problem for some users, I decided to post this workaround for converting any sense PPP build to RMNET. I have only tested this on Mdeejay Revolution build but should work with any sense build. I have used this for more than 10 days now without any problems whatsoever: everything worked like on the original build.And no data drops.
All attached files were extracted from Sergio's CoreDroid version 0.5 which is an RMNET build. Hope he doesn't mind.I am not at all a developer
The steps are outlined below:
1. Download and extract the attached files on your PC
2. Open the Android folder of your build on your PC, and copy + replace the zImage and rootfs with the extracted ones.
3. Boot into Winmo and transfer your android folder to your SD card; also transfer the extracted module folder to your SD
4. Boot into Android; after initial setup, reboot again.I recommend a clean fresh install (ie without any old data image; you may re-use your data.img after setup is complete)
5. Use Root explorer to copy and replace the 2 files in the extracted modules folder into \system\lib\modules.
6. Reboot and enjoy
Click to expand...
Click to collapse
Is it possible that this fix be included by the chefs ... because I can't really follow the instruction.
Thank you, thank you, thank you so much!
Sent from my GT-P1000 using XDA App
Did a fresh copy of mdeejay revolution 2.3 and this kernel yesterday evening. No datadrop at all! Also did the wifi and volume fix, wonderful.
Many Many Many Thanks!!!!!
WiFi Hotspot
WiFi hotspot dont works with this.
i1magic said:
Is it possible that this fix be included by the chefs ... because I can't really follow the instruction.
Click to expand...
Click to collapse
All this really does is to swap the build back to using the old nexus kernel, presumably if the chefs wanted the old kernel in their build they'd already be using it.
hastarin said:
PPP still has to reconnect if your phone hops between towers/bands but seems to do so relatively reliably now. I have no idea how RMNET handles that situation.
Click to expand...
Click to collapse
I seem to recall someone saying that it is handled by Android (as opposed to the kernel), since RMNET is the "official" way to do things in Android.
Awesome!
Thanks for making this.
Can't wait to try it with some of the great builds here.
Was getting tired of all the build lately only using busted PPP based kernels.
What good is a data phone if the data connection is a joke.
Related
DISCLAIMER: Nobody -- and I do mean nobody -- is responsible for a bricked device except for the person attempting this modification. Do not contact me to complain that you borked your Slide by not following instructions.
All credit for this discovery goes to knowmercymod
Certain Espresso owners running CM6 (or CM6 derivatives) may have discovered that their wifi functionality doesn't work as expected. The issue is well-documented on the CM6 issue tracker [issue 2153] and the cause of the problem is known, but there is no source-based solution at the moment. As such, there's no easy way to distribute a fix for working wifi within a packaged CM6 zip.
The issue relates to missing GPL'd drivers for the MSM7227 chipset from Qualcomm that is used in several devices, most notably the HTC Espresso, Legend and Aria. But due to small versioning differences in certain aspects of this chipset, some devices have functioning wifi using the generic open-source SDIO modules and others do not. The permanent solution for this issue is cajoling HTC into releasing this code -- this process is already underway -- but, in the meantime, this thread will serve to provide a temporary solution that is 100% effective.
So let's get started...
Step 1: Downloading the necessary files
Attached to this post are the two files necessary to fix this issue:
sdio.ko
tiwlan_drv.ko
They both come from *stock* Espresso -- the code currently in use in the CM6 repository does not generate fully-functional versions of these modules.
Download the "modules.zip" file to your PC and extract the two files to an easily accessible location.
Step 2: Backing up the corresponding files on your device [optional]
This optional step will walk you through backing up the existing files on your device. This is completely unnecessary as those files can simply be restored by re-flashing a CM6 zip, but I figured that people should get in the habit of backing up stock files before modifying their device.
To do so, execute the following two commands -- both can be done while the phone is booted up or in recovery (if you're in ClockworkMod recovery, just make sure your system partition is mounted -- partitions->mount /system):
Code:
ADB PULL /system/lib/modules/tiwlan_drv.ko [DESTINATION]
ADB PULL /system/lib/modules/sdio.ko [DESTINATION]
To use my PC as an example, I would connect my Slide via USB and enter the following commands on the command line:
Code:
ADB PULL /system/lib/modules/tiwlan_drv.ko ~/Documents/Android/Backup
ADB PULL /system/lib/modules/sdio.ko ~/Documents/Android/Backup
Step 3: Replacing the files on your device
So now we're ready to make the actual modification. First step: boot into recovery. My preferred method is to use the ADB REBOOT RECOVERY command.
Once you're in ClockworkMod Recovery, please make sure system is mounted -- partitions->mount /system
Then you would simply execute these two commands:
Code:
ADB PUSH [SOURCE]/tiwlan_drv.ko /system/lib/modules/tiwlan_drv.ko
ADB PUSH [SOURCE]/sdio.ko /system/lib/modules/sdio.ko
To use my PC as an example, I would enter the following commands on the command line:
Code:
ADB PUSH ~/Downloads/modules/tiwlan_drv.ko /system/lib/modules/tiwlan_drv.ko
ADB PUSH ~/Downloads/modules/sdio.ko /system/lib/modules/sdio.ko
Once you've pushed these files, simply reboot your device and you're done! You should no longer have any issues with your wifi connectivity, including (but not limited to) full wifi tether functionality when using the Wireless Tether 2.0.5 application.
And, again, all credit for this temporary fix goes to knowmercymod (who is far too humble to post this himself).
Saving this space for future updates...
I hope this fixes my frequent disconnects, but on the legend section they fixed the problem by changing the channels to 14 instead of 11, not sure if that will work for espresso.
UPDATE: Works great! Thanks for posting this.
Very exciting news! I'll fully charge and try this fix. Looking forward to using CM instead of stock.
Just pushed the files to cyanoginger 1.1.. wifi and wifi tether both appear to work perfectly now
Cool, thanks for posting!
I did it, not sure if it did anything. Weird thing is, after pushing the 2 files I noticed I forgot to mount the system folder but it said it transfered successfully.. *shrugs*
I think tethering was working before, either way though, it works now
Awesome! Thanks so much for the hard work. I know you guys will manage a perm fix via a regular rom soon. HTC will cough up that source code for ya
Just chiming in to say this works for me. Takes a little longer now to connect to an access point than it used to, but rock solid after that. With s-off, didn't even have to be in recovery, just mounted system rw, pushed files, and rebooted.
Sent from my MyTouch 3G Slide running CM6.1.1
Did it right off my phone with sufbs file manager. Great job hopefully its integrated in next cm build.
I keep getting a "out of space" error when I go to copy the files.
Please help.
poormanq45 said:
I keep getting a "out of space" error when I go to copy the files.
Please help.
Click to expand...
Click to collapse
If you have not applied s-off patch by alpharev, then you have to push the files while in clockwork recovery, after going to the partitions menu and selecting mount /system. If you are in fact s-off, you have to use a terminal emulator and type [code}mount -o rw,remount /system[/code] and then push the files
Sent from my T-Mobile myTouch 3G Slide
CM6 wifi works fine for me, but would these drivers work better with my phone anyways since they're specifically made for this phone?
Applied this on Arayaray revamped which seemed to have spotty wifi for me especially when accessing the market. After applying this the wifi is perfect not a single problem at all now, thanks so much!!
I refuse to connect my phone to my pc. Is there any way to get these files pushed onto my phone? Terminal Emulator work? If not, it's cool. Wifi seems to be working for the most part under CM6.
xaodxkevin said:
CM6 wifi works fine for me, but would these drivers work better with my phone anyways since they're specifically made for this phone?
Click to expand...
Click to collapse
It depends. These files are taken *directly* from the stock espresso rom and are known-good. If you're not having any issues with wifi running CM6 I don't feel comfortable telling you this will "improve" anything -- but I don't think it would hurt. In any case, if you follow my instructions you will have backed up the original files and can restore them at any time.
Hayzie said:
I refuse to connect my phone to my pc. Is there any way to get these files pushed onto my phone? Terminal Emulator work? If not, it's cool. Wifi seems to be working for the most part under CM6.
Click to expand...
Click to collapse
Uhhhh -- why? That seems incredibly myopic and weird. You know what -- never mind -- I don't want to know. You can use a terminal emulator on the device to move the two files from your sdcard to their rightful place on /system. I'll leave it as an exercise to the user to figure out the correct commands to do so.
Well I'll tell you anyways... MyTouch Slide always acts funny when plugged via USB to my pc, more-or-less so Windows 7. I could say this is an uncommon issue, but it's not. So it's not weird.
Mine works just fine, whats funny about it when u plug it in? Sorry to bring this up here herbrewtoyou but im curious lol
Sent from my T-Mobile myTouch 3G Slide using XDA App
Hey guys I just pushed the 2 files to my phone, I'm running CM 6.1.1-Slide - since I flashed to 6.1 and then reflashed to 6.1.1 I have had 0 Wifi capability. So I push these files and followed the instructions, and well I still have no wifi. I will enable it and it will scan, try to authenticate and then disconnect and repeat.......any ideas???
ApeMan911 said:
Hey guys I just pushed the 2 files to my phone, I'm running CM 6.1.1-Slide - since I flashed to 6.1 and then reflashed to 6.1.1 I have had 0 Wifi capability. So I push these files and followed the instructions, and well I still have no wifi. I will enable it and it will scan, try to authenticate and then disconnect and repeat.......any ideas???
Click to expand...
Click to collapse
Sounds like an issue with your router...
No its def not the router, phone would connect all day long before switching to CM.
Very Important Information For Beginners
/Introduction to Android for SD Cards
Okay, firstly I made this thread because pretty much every new person to this section of the forums is completely lost and unsure what things are or what to even do. We are also sick and tired of threads saying 'how do I get stared' or 'which is the most stable' etc.
----------------------
Download your files from here:
You will be accessing these websites quite often so it might pay to bookmark them
Kernel downloads, almost always download the top one, they are updated often (needs extracting): http://glemsom.users.anapnea.net/android2/htc-msm-linux/
Rootfs downloads, download the top one, they aren't updated as often as the kernels above but still quite regularly (also needs extracting): http://files.xdandroid.com/rootfs/
Initrd downloads, rarely updated (don't extract, just rename to initrd.gz) http://files.xdandroid.com/initramfs/ People almost never need to download one of these separately.
----------------------------------
Basic need-to-knows:
Kernel: Your modules/zImage. Your zImage always needs be in the root (first folder) of your android folder on your SD and ALWAYS named zImage, your modules should also be in the root of your android folder named modules-LOTSofNUMBERSandLETTERS.tar.gz never rename your modules. It should always be in .tar.gz EG: modules-2.6.27.46-01276-g6a6a1c1-dirty.tar.gz
Rootfs: Must be in the root of your android folder named rootfs.img
Initrd: Needs to be in the root of your android folder named initrd.gz
Data.img: Generated on the first boot of android and placed in root of android folder. Is a virtual memory file that acts as the phones internal memory for android. Holds all your settings etc. May have to be recreated some times (just by deleting it)
Haret.exe: the file executed by your Windows ROM to kick Windows out of memory and boot android.
system.ext2: Main android file, must be in the root of your android folder. Holds all of your build.
startup.txt: File that instructs android how to start up. Needs to be in the root of your SD. (I will cover this further down)
ts-calibration: A file in the android folder that holds calibration information of the touch screen.
Various Folders: You will see/have/need other various folders created in the root of your SD and in the root of the android folder, such as conf, cache, data, media etc. You usually don't want to delete these.
Root: The root folder of any partition is the "highest" folder in the hierarchy. The root folder contains all other folders and can also contain files. For example, the root folder of the main partition on your computer is probably C:\. The root folder of your DVD or CD drive might be D:\.
Also Known As: "the root"
RIL: Radio interface layer: basically controls your radio (GSM/CDMA network)
------------------------------------------------
startup.txt
VERY IMPORTANT, your startup.txt must be customized to your device. (mine is a rhod110). You can find your model number under your battery. This file belongs in the folder with your android.
My startup.txt looks like this
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 rel_path=FRX07 physkeyboard=rhod100_uk acpuclock.oc_freq_khz=710000"
boot
Now I believe you should be able to copy and use this as yours with a few slight modifications. Change rel_path= to wherever your android is stored on your sd, for example when I go to my sd inside the folder frx07 (the root of my android folder) all my android files are there. If your folder was called andboot it would be rel_path=andboot. (without that full stop) Now change your physkeyboard= to your model of your phone, mine is rhod110 but the rhod100_uk keymap is EXACTLY THE SAME AS THE RHOD110 so that's why I use rhod100_uk instead of rhod110 (rhod110 isn't recognised by frx07), this is important to make sure your keys are assigned properly.
------------------------------------------------
Models of rhod:
From what I know that exists. If you find one not listed, make sure you tell me so I can update the list
rhod110 uses rhod100_uk and it works as it should
These can be used for physkeyboard= in startup.txt (needs updating, some may no longet be supported because F22 hasn't commited old changes)
rhod100_de
rhod100_es
rhod100_fr
rhod100_it
rhod100_nl
rhod100_nordic
rhod100_uk
rhod210
rhod300 (tilt2)
rhod400
rhod500
Getting set up:
Go to http://forum.xda-developers.com/showthread.php?t=1171052 and download the FULL BUNDLE
Other builds exist such as gingerbread but this guide only covers froyo frx07.
Replace/add the Kernel from the downloaded build with the latest one (remember this is the zImage and modules-NUMBERS.tar.gz). Updating is as simple as this, do it often - there is no data loss. See links mentioned above for links. Making sure that the (if there were) old kernel files are all deleted and the new ones are called zImage and modules-NEWdifferentNUMBERS.tar.gz
Replace/add the rootfs.img with the latest one from the link above it should be named rootfs.img.
Remember that the rootfs and kernel are updated quite often and that you should check and update every few days.
Make sure your startup.txt is correct and make sure everything is where it should be in a folder on your computer, then copy the folder to the root of your sd card.
Navigate to this folder using the file explorer in your Windows ROM (YOUR PHONE) and run the Haret.exe
It will then have some writing running down a black screen before booting android (it's just preparation to booting) read it if you want
Android will start and you should leave it about 2-5 minutes before touching anything, it has things running in the background and it will be slow, still setting itself up. Navigate to settings and set up your phone. If anything goes too badly wrong you can always delete data.img and start again! Data.img is the internal memory of the phone, remember? Well, until we get android working on the real internal memory...
---------------------------
Structure:
My SD card. (with android on it)
I'm running:
kernel: 20110819_183957 http://glemsom.users.anapnea.net/android2/htc-msm-linux/
build: Froyo FRX07http://forum.xda-developers.com/showthread.php?t=1171052
rootfs: rootfs-20110816-7e04198.zip from http://files.xdandroid.com/rootfs/
Code:
EncFiltLog.menc
kbd_info
Android
cache
download
tmp
Private
Games
Installs
DCIM
Others
Videos
Images
Sounds
media
frx07
rhodimg.nbh
My android is in frx07
inside my frx07:
Code:
data.img
ts-calibration
startup.txt
modules-2.6.27.46-01348-g9de837f.tar.gz
zImage
haret.exe
initrd.gz
system.ext2
AndroidApps
conf
media
rootfs.img
-----------------------------------------
Backup/Restore
when you have the need to backup and restore data, look for an app called Titanium Backup. I have never used it but heard it works brilliantly, even backing up your apps! There is a 'donation' version and a free version with not many differences. I suggest you go check it out!
-----------------------------
USB CONNECTIVITY
When your phone is in Android you can not use it like a USB, HTC's drivers will not work and you have to use certain programs until this is implemented.
Windows: Install DroidExplorer this lets you open a terminal (like command prompt) on the phone, lets you browse device adding/deleting files, among other features that are very useful. If that DroidExplorer doesn't pick up your phone (when picked up it will be called 0000000000) install PDAnet on your phone and pc. PDAnet provides the drivers needed to connect the phone. It also lets you use your phone as a modem and you can send SMSs using your computer. Do NOT run PDANET at the same time as DroidExplorer. When PDANET is connected it WILL use your phone for data connections - this is the only warning. The phone is not used for any networking when DroidExplorer is connected.
Mac: Unknown to me (can someone post?)
Linux: Never tried, it is easier than windows (can someone post a method?)
---------------------
Overclocking
Do NOT overclock WINMO.
If you want to overclock your device do so at your own risk.
it is as simple as adding "acpuclock.oc_freq_khz=710000" without quotes to your startup.txt cmdline. 710000 (approx 710 mhz) can be swapped for any number but this is practically the highest stable speed achievable. I use 710000, works fine for me.
-------------------------
Known problems across ALL BUILDS:
Media Player Some tracks might have playing issues. FIX: HERE
Bluetooth is experiemental
Speakerphone static : seemingly random issue
USB plugging the device into a computer, it will be recognised, but not by HTC drivers. FIX: You must use something like DroidExplorer and PDAnet to browse the device and ADB (android debug bridge). See above ^^ (USB tethering is being fixed/has been fixed)
FN LED On keyboard the caps LED works but the FN LED currently does not. FN still works fine
No deep sleep: FIX: disable GPS (or kill the running app causing phone to not sleep)
Failure booting Android: Phone fails to enter android after running haret.exe FIX: Make sure your winmo is NOT overclocked before booting android.
Booting or SD Card related problems: Make sure your card is formatted as FAT32 (reformat as Full Format if it is not working)
More information is available on the wiki, there is also information there if you want to get into development. There is a pretty good FAQ on that wiki too
Remember XDAndroid is not just for this device.
If any of this is wrong or you think something should be updated/changed, please tell me
The CDMA startup should have "board-htcrhodium.is_cdma=1" instead of "...is_gsm=0"
otherwise, looks good!
AkumaX said:
The CDMA startup should have "board-htcrhodium.is_cdma=1" instead of "...is_gsm=0"
otherwise, looks good!
Click to expand...
Click to collapse
Indeed, there is no "is_gsm" command .
arrrghhh said:
Indeed, there is no "is_gsm" command .
Click to expand...
Click to collapse
Thanks to both of you, not bad considering I don't even have a cdma phone eh?
anything I need to add? I will tidy it all up soon
Something that might catch out a beginner is if they have an older SD card and it isn't detected by more recent kernels.
Need to include this in the cmdline:
msmsdcc_1bit msmsdcc_fmax=14000000
the.decoy said:
Something that might catch out a beginner is if they have an older SD card and it isn't detected by more recent kernels.
Need to include this in the cmdline:
msmsdcc_1bit msmsdcc_fmax=14000000
Click to expand...
Click to collapse
I thought this was squashed in recent kernels?
arrrghh said:
saneksem said:
add that to startup,helped me on 2 gb card
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
Click to expand...
Click to collapse
You don't need this if you're on a newer kernel!!!!
Just update your kernel folks, no need for this in the startup!
Click to expand...
Click to collapse
Oh, ok. I must have missed that. I only needed it on my older SD which I haven't tried using for a month or so.
I guess the only thing I would suggest (all minor things) would be maybe to bold/underline keywords, like "kernel", "rootfs", etc.. to differentiate things that may change over time; ex: I'm running FRX05 system.ext2, 3/1/11 rootfs from F22, 3/1/11 zImage/modules (kernel) from arrgghh, etc... And, I guess you "could" be nice and show people what they could edit in the startup.txt, depending on their phone; ex: I'm Sprint, so I would do kb=rhod400, cdma=1, etc..., but for each phone.
I would probably have to do all the different startup.txt's in a different thread, unless I just provide a quick table... I will think about it however I do like the idea about bolding key words.
Most new people don't realize if they have their call/end/windows/back buttons on in winmo, they will stay on while on android and never go off. Might want to put that in your first post before telling them to run haret...
at the end where you say you can just delete the data.img and startover its probably a better idea to say to be patient and reboot the phone once or twice before ditching your data.img ! and creating it is the bulk of the first boot, the linux black screen with the scrolling words section.
you can talk about saving your data.img just incase something goes wrong.
titanium backup is a must
having an app that can save sms when you switch builds (not a big deal for everyone but important to some.)
also let new users know android isn't perfect, things randomly completely mess themselves all the time, don't get discouraged just start fresh with a format and new files when deleting the data.img doesn't work and you'll be just fine.
All I want to know now is if I have helped anyone yet and if they had any problems with any part of it or want me to clarify anything I will be quite happy with such replies ^-^
Is anyone able to provide me with some ETAs of fixes on the problems across all builds listed in the OP? Also are there any more I am not aware of? Oh and if anyone is working on them?
Much Appreciated
ryannathans said:
Is anyone able to provide me with some ETAs of fixes on the problems across all builds listed in the OP? Also are there any more I am not aware of? Oh and if anyone is working on them?
Much Appreciated
Click to expand...
Click to collapse
There's never an ETA for anything getting fixed - BT seems close, but who knows the exact date it will be done? As CyanogenMod says, the only rule is don't ask for release dates / ETA. It'll be ready when it's ready.
Some problems are being looked into more than others, but I wouldn't say one in particular has been left out to rot. jb is fixing up BT, entropy is working on GPS fixes, wistilt2 on the RIL of late... Basically devs pickup things that are of an interest to them to fix. There's a lot still to fix/cleanup, so taking it all on alone is a little daunting. Gotta break it down into smaller pieces so it's at least somewhat manageable.
Thanks and a question...
First, thanks for the awesome post - quite helpful...
Second: I haven't mussed with my phone for about a year, for various reasons, the main one being that I was happy with my previous phone and the ROM I finally settled on, the secondary one being that phone died, and I now have a (blech) Sprint TouchPro2 (RHOD400), and am on my sixth (yes, sixth!) brand new TP2 - they keep giving me a new one because of problems (things, like... oh... say, not being able to answer calls... kind of a basic function in a mobile phone, nah?!) And, I've had no interest in futzing with what is already a frustrating and non-functional phone. I was hoping I could upgrade instead of getting another TP2 the last time I brought it in for probs, but they would only downgrade me to worse phones. So... here I am, wanting to put Android on my phone and see if there is any improvement. Or, at the least, be able to utilize some of the decent progz/gamez for Android. I mean, if I can't answer calls, at least I can use it as a handheld gaming system, right?!
Long story short: when I was flashing ROMs to other phones, the instructions explicitly said that you needed to unlock, etc., first. I can't find any data re: if there are steps you must take on your phone to 'prep' it, *before* following the steps in this thread. I've browsed the DB and no luck.
My apologies for being an annoying n00b!
PS: one of my friends said "Tell 'em you're a hawt babe - then they'll help for sure!" (ROFL)
And, thanks, again!
Tynkrrbell said:
Long story short: when I was flashing ROMs to other phones, the instructions explicitly said that you needed to unlock, etc., first. I can't find any data re: if there are steps you must take on your phone to 'prep' it, *before* following the steps in this thread. I've browsed the DB and no luck.
My apologies for being an annoying n00b!
And, thanks, again!
Click to expand...
Click to collapse
Well the reason you can't find any info on it, is that it's not required .
These builds run entirely off of the SD (currently - I wouldn't try NAND yet, it's in its infancy) so there's no need to do any HardSPL or anything really to prep - just drop the bundle on your SD card - if it's at the root, run haret.exe and gogogo!
Oi. I get the stupidcard of the day!
That is awesome! Same friend that suggested I mention I am a 'hawt babe' said I should "give boobpr0n" to whomever helped me. You probably wouldn't want to see that, though!
You are heartily appreciated! I'm off to be an Androidite!!!!!!
Tynkrrbell said:
That is awesome! Same friend that suggested I mention I am a 'hawt babe' said I should "give boobpr0n" to whomever helped me. You probably wouldn't want to see that, though!
You are heartily appreciated! I'm off to be an Androidite!!!!!!
Click to expand...
Click to collapse
My gf suffices for that .
Hope you enjoy Android!
Tynkrrbell said:
That is awesome! Same friend that suggested I mention I am a 'hawt babe' said I should "give boobpr0n" to whomever helped me. You probably wouldn't want to see that, though!
You are heartily appreciated! I'm off to be an Androidite!!!!!!
Click to expand...
Click to collapse
Not to burst any bubbles here, but if you are saying you are a "hawt babe" and give boobpr0n mumbo jumba, you are prolly not one and won't give it anyways.. so nobody will most likely believe you here..
Good luck though~
After many hours of research and trial and error we finally have a working Wifi setup on CM7!
This is what we learned:
-There are specific wifi drivers that must be compiled alongside the kernel (twilan_drv.ko)
-The .ini file are developed when building the drivers that also must be used
-The stock firmware.bin file can be used
-The wifi drivers must be calibrated to work properly and efficiently. This can be done by referencing the WifiBackupConfiguration file found on the /Rom partition
-This device uses the Ti wl1273 wifi/Bluetooth card but is compiled using the wl1283 drivers (The Kindle Fire drivers worked perfectly! Boo you B&N for the no-show)
Here are some simple steps to get it working on your device:
1. Build a kernel (there are several other threads that talk to this like: http://www.nooktabletdev.org/index.php/Making_a_Boot_Image)
2. Get the Kindle Fire Source: http://kindle-src.s3.amazonaws.com/Kindle_src_6.2.2_user_3205220.tar.gz
3. Build the drivers:
Code:
cd <path to KF source>/Source/mydroid/hardware/ti/wlan/wl1283/platforms/os/linux/
make ARCH=arm CROSS_COMPILE=/opt/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi- KERNEL_DIR=<path to NT source>kernel/android-2.6.35 TNETW=1273
cd ../../../..
cd wl1283_softAP/platforms/os/linux/
make ARCH=arm CROSS_COMPILE=/opt/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi- KERNEL_DIR=<path to NT source>kernel/android-2.6.35 TNETW=1273
NOTE: You can use whatever Cross Compiler you want. I found the most success using CodeSourcery Lite (2009 or 2010) for Ubuntu 11.10. Another common path is
Code:
~/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
If you are getting build errors it is probably because your kernel path is wrong or you need to try another set of CROSS-COMPILER files.
Note the line 'TNETW=1273' when building. That is the key to building the correct driver version.
4. Copy the drivers and ini files to your /system/etc/wifi folder:
Grab the twlan_drv.ko from the wl1283/platforms/os/linux folder. Also grab the tiwlan.ini file from wl1283/platforms/os/linux folder. Push both of these to your /system/etc/wifi folder.
Next grab the tiap_drv.ko and tiwlan_ap.ini from the wl1283_softAP/platforms/os/linux/ and wl1283_softAP/config folders. Push these to the /system/etc/wifi/softap folder.
5. Ensure your init.omap4430.rc has access to WifiBackupConfiguration
6. Build and install your boot.img using the kernel from step 1
Done! Enjoy the internet again
So, now all that needs to be fixed is SOD? Good news, thank you all for your hard work.
Mephikun said:
So, now all that needs to be fixed is SOD? Good news, thank you all for your hard work.
Click to expand...
Click to collapse
Fixing SoD should be usable enough for first Alpha. Then it is tweaking small things, having everyone find bugs, and fixing them!
Goncezilla said:
Fixing SoD should be usable enough for first Alpha. Then it is tweaking small things, having everyone find bugs, and fixing them!
Click to expand...
Click to collapse
Can't wait to start testing and finally help with the development
If bluetooth is on the same chip as wifi, will this also make bluetioth function?
travisn000 said:
If bluetooth is on the same chip as wifi, will this also make bluetioth function?
Click to expand...
Click to collapse
As of right now bluetooth does not function with these drivers (even though it is turned on in the kernel).
There are however some init.omap4430.rc services that look like they could be enabled to activate blutooth. We are going to try this out soon but are currently working some higher priority functionality issues.
I'll be sure to ammend this thread if we get blutooth working
Gentlemen,
Lately I have found myself experimenting with Debian on my beloved Leo. It's very much WIP, but even right now it may be fun to play around for some. And most of the stuff that *doesn't* work, well, solutions are in the line of sight.
I won't have time to finish it anytime soon. So, partly in hope someone will join the effort, and partly to simply make sure I won't lose effects of my work in the darkest corners of my hard drive, I upload it as it is.
It's very much bare-bones Debian Unstable system. To install it, copy all three unpacked files (rootfs.ext4, zImage, initrd.gz) to "debian" directory on your SD card. Then, choose this directory in MAGLDR settings. Then boot from SD.
It boots directly into the desktop and allows you to connect to wifi and launch terminal (and install any software you want using apt-get/aptitude).
DOWNLOAD:
http://www.multiupload.nl/8D7ZS99UTX
http://d-h.st/Tx9 (thanks to Robbie P)
MD5: 9f5a9961d8ace10d38f7ea493a12ab4a
(mirrors appreciated)
Features:
*Touchscreen, UI works perfectly fine
*Wifi works perfectly fine too
*Sound kinda works (playback is too fast for me, please test)
*It's full Debian GNU/Linux - 15901141666 packages to apt-get!
Various technical info:
*Kernel based on linux_on_wince_htc from gitorious with some modifications:
-applied USB host patch by liiochen
-applied patch from tytung kernel that enables ALSA driver to be compiled as module (without that it wouldn't work at all)
-custom defconfig
*Rootfs size is 1GB. Filesystem is ext4 (to avoid data corruption).
*Window manager is E17, it's optimized for phones, very beautiful, and very impressive overall. Network manager is Wicd.
*Also installed: Xterm, SSH server.
*Default username is "htcleo". Default password for this account is "htcleo". Default root password is..."htcleo".
*As it is Debian Unstable, anything can break at any time and not much can be done about it. I also recommend using aptitude over apt-get (it is better at solving dependency problems).
Important To-Do:
*Phone functionality & suspend/resume (all of this should be supported! sadly, fso-deviced in Debian repositories is currently broken)
*Landscape mode (easy)
*Hardware buttons (easy)
*Bluetooth (at least partial support should be easy)
*??? to be continued
Wish-list (the less important stuff):
*Switch to armhf for performance gains (should be easy)
*At least partial hardware acceleration (should be possible thanks to xf86-video-msm driver)
*Bully someone into cooking newer kernel (2.6.32 is old)
*If the above doesn't work, backport brcmfmac wifi driver to current kernel
*Compass, GPS, camera, multitouch (aka the stuff not many really care about)
*??? to be continued
If you want to help me in the effort to make this port work perfectly, take a look at this:
http://www.multiupload.nl/BXNBMMECH0
It's a package with everything you need to reconstruct my rootfs on your own. There are some files and there is a dirty bash script ("createrootfs") that does everything that has to be done. Instructions are inside of it.
There is a lot of valuable information on htc-linux wiki (http://htc-linux.org). I'm available in this topic, on pm, and on #htc-linux freenode channel.
Big thanks to #htc-linux, Cotulla, liiochen, tytung, dcordes, many others I forgot about and will add later.
[EDIT 16.09.12]
Some people requested kernel sources, here they are:
http://www.multiupload.nl/IWL07GL78D
MD5: c698454af38ad7ed3dbec120eae84daa
Clever ones will notice ".git" subdirectory. There's full history and anyone's more than welcome to upload it onto github/gitorious/similar.
Please refer to this htc-linux wiki page for compiling: http://htc-linux.org/wiki/index.php?title=QuickDeveloperStartGuide#Kernel . Use htcleo-gnu_defconfig (it's in arch/arm/configs/ directory).
I would appreciate someone testing USB host functionality. It should work (proper patches were applied), but I don't have cables to check it out myself.
Won't load from magldr-stop on " 123fatal hit 3 "
Sent from my HTC HD2
USB host works, keyboard and mouse. Connected to wifi ok. But when I tried to take a screenshot, it just hung and had to press soft reset button. Will test more.
Excellent work bardzusny, BTW there are Ladies on this forum too
@ivicabrus, be sure to unzip the .tar.gz, the .tar and also the rootfs.zip
Edit; mirror- http://d-h.st/Tx9
In my debian folder...is it correct?
Sent from my HTC HD2
ivicabrus said:
In my debian folder...is it correct?
Sent from my HTC HD2
Click to expand...
Click to collapse
Looks good m8
Robbie P said:
Looks good m8
Click to expand...
Click to collapse
But won't load..
Sent from my HTC HD2 using xda premium
ivicabrus said:
But won't load..
Sent from my HTC HD2 using xda premium
Click to expand...
Click to collapse
magldr>10.services>1.bootsettings>1.bootsource>3.AD SD Dir>DEBIAN
maldr>2.boot ad sd
Did you do the above?
Edit; magldr 1.13?
Robbie P said:
magldr>10.services>1.bootsettings>1.bootsource>3.AD SD Dir>DEBIAN
maldr>2.boot ad sd
Did you do the above?
Edit; magldr 1.13?
Click to expand...
Click to collapse
Yes,do everything and mgldr 1.13 i have android 4 on nand , ext 512 on sd card 8gb class 6, android load but this stop on 123 in magldr when load zlmage and initrd.gz
Sent from my HTC HD2 using xda premium
ivicabrus said:
Yes,do everything and mgldr 1.13 i have android 4 on nand , ext 512 on sd card 8gb class 6, android load but this stop on 123 in magldr when load zlmage and initrd.gz
Sent from my HTC HD2 using xda premium
Click to expand...
Click to collapse
Try 10.services>1.bootsettings>1.boot source>1.android from sd
Then the above
@Robbie maybe is problem my nand partition 220mb for android?
But debian load from sd...no understand
Sent from my HTC HD2
Will test it
Sent from my HTC HD2
ivicabrus said:
@Robbie maybe is problem my nand partition 220mb for android?
But debian load from sd...no understand
Sent from my HTC HD2
Click to expand...
Click to collapse
did you check md5 sum of download, else can't think why it isn't booting for you.
searching fatal hit 3 only brings up someone who dropped their phone
I cant boot too. But i use a2sd script in nand droid. Its that?
Sent from my HTC HD2 using XDA
[zozi] said:
I cant boot too. But i use a2sd script in nand droid. Its that?
Sent from my HTC HD2 using XDA
Click to expand...
Click to collapse
Can you boot sd android builds?
It could be that any ext partition confuses matters IDK.
humm i dont test if i can boot sd android builds... but now i can boot but, after a few code lines the hd2 reboots automaticly...
[zozi] said:
humm i dont test if i can boot sd android builds... but now i can boot but, after a few code lines the hd2 reboots automaticly...
Click to expand...
Click to collapse
Check my post earlier you have to unzip the rootfs.zip too
There is no link on the download page.
Must register on this site to be able to see the download link?
Sorry, is the first time I come across this download site.
Thanks.
Your rootfs.ext4 seems destoryed.
Sent from my HTC HD2
I did some test on this build and performance is much better than ubu. Ui is very smooth and keybord is good as for smartphone. Tried to test sound but clicking mplayer does not give result. Wifi works but sometimes needs system restart to connect. Dont try screenshot option (just like above). Good work!
Sent from my HTC Sensation (HD2) using XDA
This build is ported from http://forum.xda-developers.com/showthread.php?t=1773115 using Portadroid http://forum.xda-developers.com/showthread.php?t=1094372 (thanks boonbing), with modified initrd.gz from smokin901 (huge thanks) and loads of help and advice from wis1152 (huge thanks too)
Credits and thanks to smokin901, tytung, boonbing, texasice, evervolv team, securecrt, Bexton, wis1152, Xylograph, Rick_1995, ankuch, Zergra, Cotulla, DFT and all others, sorry if I have missed any
The LNE team are not developers, but hope to be able to provide ongoing support for this thread.
Instructions:
Well you know just extract everything and put the build folder (the one with all the files in, for example ics, jelly) in the root of your sd card. If WM6.5 tap on clrcad (nothing appears to happen) then haret, if magldr navigate to build folder using ad-sd dir and select build folder name then boot AD SD.
For help with NativeSD, visit the Wiki: http://forum.xda-developers.com/wiki/HTC_HD2/NativeSD
Please remember to REBOOT X 3.
Magldr users can get different sized blank data.ext4 from here http://forum.xda-developers.com/showpost.php?p=24930501&postcount=1353 edit; may get boot loops, please test. Magldr default=512Mb if you leave empty. edit2 here is blank 256mb one http://www.mediafire.com/?ey40c1wti77ni2w
Latest Kernels can be found here http://forum.xda-developers.com/showpost.php?p=29248688&postcount=4 but default runs well. Remember to back up before changing kernels (system.ext4 and data.ext4 just in case)
BETA 4 AOSP Native SD
Instructions for using nativeSD method can be found here http://forum.xda-developers.com/showthread.php?t=1869673 and here http://forum.xda-developers.com/showthread.php?p=31879534#post31879534 (Thanks mengfei)
This includes latest securecrt kernel but does not include journalling-off choice at install.
Download http://d-h.st/yCv
BETA 3 AOSP Native SD
Instructions for using nativeSD method can be found here http://forum.xda-developers.com/showthread.php?t=1869673 and here http://forum.xda-developers.com/showthread.php?p=31879534#post31879534 (Thanks mengfei)
Download http://d-h.st/eZD
BETA 2 AOSP
Note that first boot will take about 10 mins (depending on size of data.ext4 created) and will end with the phone rebooting. Second boot will take less time and will show the boot animation (as opposed to portadroid screen in first boot). You are porting this build, it is so that some apps are put in data.ext4 file. You can safely delete root_tmp folder after second boot to save space. Remember to reboot x3. See parent thread for changelog. Use a 3rd part app for camera (eg camera illusion)
DownloadMEDIAFIRE LINK
BETA 1 AOSP
Note that first boot will take about 10 mins (depending on size of data.ext4 created) and will end with the phone rebooting. Second boot will take less time and will show the boot animation (as opposed to portadroid screen in first boot). You are porting this build, it is so that some apps are put in data.ext4 file. You can safely delete root_tmp folder after second boot to save space. Remember to reboot x3. See parent thread for changelog. Use a 3rd part app for camera (eg camera illusion)
Download MEDIAFIRE LINK
Version 6 alpha
Note that first boot will take about 10 mins (depending on size of data.ext4 created) and will end with the phone rebooting. Second boot will take less time and will show the boot animation (as opposed to portadroid screen in first boot). You are porting this build, it is so that some apps are put in data.ext4 file. remember to reboot x3. See parent thread for changelog. Use a 3rd part app for camera (eg camera illusion)
Download http://www.mediafire.com/?ciqjcy49tcfgcc8 md5sum=b807764b3d9b3b942a4654be8c09eee7
Version 5 alpha
Build folder is ics again
Note that first boot will take about 10 mins (depending on size of data.ext4 created) and will end with the phone rebooting. Second boot will take less time and will show the boot animation (as opposed to portadroid screen in first boot). You are porting this build, it is so that some apps are put in data.ext4 file. Remember to reboot x3. Unfortunately stock camera does not work, try camera360 from playstore or see http://forum.xda-developers.com/showpost.php?p=29749517&postcount=460 (please do not post anything on that thread)
Download http://www.mediafire.com/?wpf8j34r2j82jug md5sum=aa83b79d2624657a22ff36376d1c6b97
Version 4 alpha
Build folder is ics again
Download http://www.mediafire.com/?ibbcpxywlf6wals md5sum=c25ddc38d49e141414fc67ed069bab83
Version 3 alpha
smokin901 has been busy in the early hours and has fixed sd mounting problems for us sd users-THANK YOU again smokin901. Also working USB Mass storage Mode, Browser, Installing Apps on SD card, Superuser (included app and binary already in the rom)- can install superSU if problems. Build folder is called ics again. A fix for the camera can be found here http://www.mediafire.com/?3bh08l3xttte5am (put meta-inf and system in sdcard/ics/root folder and reboot). Though camera works display is grainy but pictures are clear-Credit to Zergra (see http://forum.xda-developers.com/showpost.php?p=29124206&postcount=239 and press the thanks button there )-"Video Recording is buggy"
Download http://www.mediafire.com/?s8l1u85iczoo62i md5sum=a5bc0752b2d840db0f07f3f94236137c
Mirror http://d-h.st/YnL
Version 2 pre-alpha (haret)
After hours and hours (since 4AM this morning) wis1152 has managed to port a version for haret (&magldr BTW) users with working data and root. Huge respect and thanks.
Please do a fresh install as root seems to still be broken if using an existing data.ext4, set your size in startup.txt. Note that folder is called ics in this build, rename if neccessary (and edit startup.txt accordingly).
Download http://d-h.st/Plq
Mirror http://www.mediafire.com/?6h8jhji8ytnh86n
Version 2 pre-alpha
We have root, google now and data working (data for magldr users only ATM, haret users can try changing kernel, but may lose root). Note that install folder is called jelly. For browser, try chrome or other browser from this list http://forum.xda-developers.com/showpost.php?p=28841137&postcount=70
Download http://www.mediafire.com/?wneyk8ibcuqx4ju md5sum=d18c33c4b92a493e1872290f946de2fa
mirror http://d-h.st/X9d
Version 1 pre-alpha
Remember this is a work-in-progress, things may not work. For example root privileges, Camera, Browser works but display is messed up, Error when Installing some Apps, Google Now crashes.
Download http://www.mediafire.com/?55d95qd2ycyld52 md5sum=3730a6c9f01a1fc3da0c1dd4e1113f41
Mirror http://d-h.st/S0k
<>
Pre-alpha versions 1&2 and alpha 3,4&5 softkeys
See http://forum.xda-developers.com/showpost.php?p=29034218&postcount=166
Put system and meta-inf into /sdcard/ics-or-jellyb/root folder and reboot
As far as I can see it adds 2 lines to /system/build.prop
Code:
qemu.hw.mainkeys=0
qemu.sf.lcd_ density=110
Not sure why lcd density is put to 110, it has no effect on actual lcd density.
Anyway, delete these lines to remove softkeys and before rebooting, make sure your root folder is empty, else it will re-install (yes, it happened to me)
You may find the some screens slightly messed up with softkeys added.
No soft power key yet. Try Quick Boot from market and add power off widget to homescreen, thanks liuhung.
Pre-alpha version 1 only
Softkeys can be got from here http://forum.xda-developers.com/showpost.php?p=28874557&postcount=92
Put system and meta-inf into /sdcard/jellyb/root folder and reboot
To remove, use the attached instead (it has original .apk)
For magldr users, a way to change ro_lcd_density in /system/build.prop without root permissions was found by vikingzou here http://forum.xda-developers.com/showpost.php?p=28292160&postcount=614 genius.
The attached below is for pre-alpha 1 release only
<>
Google now screenshot
And link to bexton's jellybean vid http://forum.xda-developers.com/showpost.php?p=28960523&postcount=168
http://m.youtube.com/#/watch?desktop_uri=/watch?v=JFIgUy14dwA&v=JFIgUy14dwA&gl=GB
Mine.............
Sent from my GT-I9100 using xda premium
Robbie P said:
This build is ported from http://forum.xda-developers.com/showthread.php?t=1773115 using Portadroid http://forum.xda-developers.com/showthread.php?t=1094372 (thanks boonbing), with modified initrd.gz from smokin901 (huge thanks) and loads of help and advice from wis1152 (huge thanks too)
Credits and thanks to smokin901, tytung, boonbing, evervolv team, securecrt, wis1152 and all others, sorry if I have missed any
I am not a developer, but I hope to be able to provide ongoing support for this thread.
Instructions:
Well you know just extract everything and put the jellyb folder in your root of sd card. If WM6.5 tap on clrcad (nothing appears to happen) then haret, if magldr navigate to jellyb folder using ad-sd dir and select jellyb folder then boot AD SD.
Please remember to REBOOT X 3
Magldr users can get different sized blank data.ext4 from here http://forum.xda-developers.com/show...postcount=1353
Latest Kernels can be found here http://forum.xda-developers.com/show...90&postcount=4
Remember this is a work-in-progress, things may not work.
Download http://www.mediafire.com/?55d95qd2ycyld52
Click to expand...
Click to collapse
everything works??
trezack said:
everything works??
Click to expand...
Click to collapse
If everything worked, it would be final
wifi, data, usb, video, bluetooth, sound, calls ....working, you tell us
Robbie P said:
If everything worked, it would be final
wifi, data, usb, video, bluetooth, sound, calls ....working, you tell us
Click to expand...
Click to collapse
just want to know before i delete my ics from phone is this build lagging cause first ics ported to hd2 was about 1 FPS ...i dont wanna to lose my savegames and other things if this rom doesnt work well
loop boot with side 256 data.
magldr boot
---------- Post added at 08:44 PM ---------- Previous post was at 08:40 PM ----------
with default (auto created) boots well
there is no camera app installed
Awsome !
Will try.
Thanks Robbie P, wis1152 and everyone involved.
Regards
Robbie P said:
This build is ported from http://forum.xda-developers.com/showthread.php?t=1773115 using Portadroid http://forum.xda-developers.com/showthread.php?t=1094372 (thanks boonbing), with modified initrd.gz from smokin901 (huge thanks) and loads of help and advice from wis1152 (huge thanks too)
Credits and thanks to smokin901, tytung, boonbing, evervolv team, securecrt, wis1152 and all others, sorry if I have missed any
I am not a developer, but I hope to be able to provide ongoing support for this thread.
Instructions:
Well you know just extract everything and put the jellyb folder in your root of sd card. If WM6.5 tap on clrcad (nothing appears to happen) then haret, if magldr navigate to jellyb folder using ad-sd dir and select jellyb folder then boot AD SD.
Please remember to REBOOT X 3
Magldr users can get different sized blank data.ext4 from here http://forum.xda-developers.com/show...postcount=1353
Latest Kernels can be found here http://forum.xda-developers.com/show...90&postcount=4
Remember this is a work-in-progress, things may not work.
Download http://www.mediafire.com/?55d95qd2ycyld52 md5sum=3730a6c9f01a1fc3da0c1dd4e1113f41
Mirror http://d-h.st/S0k
Click to expand...
Click to collapse
Thanks Robbie my dear friend,
will wiait for a few days awaiting reactions of other users before I install it, cause I need a working version for my work. But, nevertheless, thanksf or posting JB! at this very moment!!!
Congrats with your new site!!!!!!!!!!!
very best regards, Kuzibri
P.S. How do you like Artemis??
trezack said:
just want to know before i delete my ics from phone is this build lagging cause first ics ported to hd2 was about 1 FPS ...i dont wanna to lose my savegames and other things if this rom doesnt work well
Click to expand...
Click to collapse
the folder is named differently anyway. you can keep your existing build in ics folder, as long as you have space on sd card. It isn't laggy.
P.S. How do you like Artemis??[/QUOTE]
Seems good for now, not much time to play with it, but is solid.
Will probably go to magldr again soon when Ansar releases new WP7 ROM
Robbie P said:
P.S. How do you like Artemis??
Click to expand...
Click to collapse
Seems good for now, not much time to play with it, but is solid.
Will probably go to magldr again soon when Ansar releases new WP7 ROM[/QUOTE]
Have you read the latest developments regarding Artemis? The new version will be equipped with Microsoft Windows Embedded Mobile, so not WinMO 6.5.5 anymore. This means that the startup screen also changes to that! Great new developments are coming to us and our HD2!!!
Keep track of this my dear friend!!
It's about the same impact as JB versus ICS!!
very best regards, Kuzibri
kuzibri said:
Have you read the latest developments regarding Artemis? The new version will be equipped with Microsoft Windows Embedded Mobile, so not WinMO 6.5.5 anymore. This means that the startup screen also changes to that! Great new developments are coming to us and our HD2!!!
Keep track of this my dear friend!!
very best regards, Kuzibri
Click to expand...
Click to collapse
You know I will keep track of it. Hopefully it will include support for the new magldr too when it is released by DFT (Fingers crossed).
dimdimdim said:
loop boot with side 256 data.
magldr boot
---------- Post added at 08:44 PM ---------- Previous post was at 08:40 PM ----------
with default (auto created) boots well
Click to expand...
Click to collapse
Hi dimdimdim, sorry missed your post. I will remove the link if someone can confirm this. And make some more for JB when I get time.
trezack said:
there is no camera app installed
Click to expand...
Click to collapse
No need for the Camera when it doesn't work just yet.
Robbie P said:
Hi dimdimdim, sorry missed your post. I will remove the link if someone can confirm this. And make some more for JB when I get time.
Click to expand...
Click to collapse
no problem.
runs much smoother than ICS even in pre-alpha state..
So far so good...
I've noticed we have x2 calendar icons and x2 gallery icons.
There's no camera apk so i installed procapture but it failed to start the camera.
Tried Wifi and it works ok
Battery drains seems ok too.
This is what i have so far...
Regards