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.
I have been working on CM7 based on ambrice's work in this (http://forum.xda-developers.com/showthread.php?t=1540255) thread.
I have found that if I use adb to enable/disable wifi it is more reliable (working logcat.txt attached). If I use the GUI in CM7 it hangs up with wpa_supplicant errors (broke logcat.txt attached).
This is my first go with trying to dev any android code, so any assistance would be appreciated.
EDIT: Upon further testing it appears the issue is related to com.android.settings. If I kill the process for it, and start wifi, it works. Otherwise, I get an error on the screen stating "Application Settings (in process com.android.settings)is not responding.
Maybe you could try replace com.setting.apk with defual gingerbread com.setting.apk and look that doesnt make errors or replace WPA_suplicant, the defual one from gingerbread
Sent from my GT-I9000 using XDA
Arlicc said:
Maybe you could try replace com.setting.apk with defual gingerbread com.setting.apk and look that doesnt make errors or replace WPA_suplicant, the defual one from gingerbread
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
Just tried two things:
1. replaced Settings.apk with one from my NookColor running CM7. Same result. It works fine on my NC.
2. Pulled Settings.apk from backup of stock rom. It won't even open.
Any other ideas?
So, I don't think my first theory is good.
When I run modprobe dhd and check the sockets folder out is empty. I verified dhd was loaded with lsmod.
I also tried to start wpa_supplicant manually and it states eth0 does not exist.
I'm starting to think it's a kernel or driver issue.
Sent from my SGH-I777 using xda premium
Hi I've been looking over the forums on information about this but i cannot find out how to add drivers to a ROM
i don't have a backup of the stock ROM, however i have a ROM in which everything apart from WiFi works ( 5 point touch screen, all hardware buttons, sound, screen)
this Q88 ROM is downloaded from http://lctrading.hk/download/Q88/
i tried the cyanogenmod ROM from ANONFBI
http://forum.xda-developers.com/showthread.php?t=2343531
and nothing works apart from the wifi driver no touch, no volume buttons
i would like to extract the drivers from the q88 rom and add them to the cyanogenmod rom.
ive never been able to get the camera working its the single front camera it doesnt bother me its not very good
i tried this thread http://forum.xda-developers.com/showthread.php?t=2189569
however when i load a driver the ported PORTED JB-4.1.1 rom doesnt boot up
i see it has camera drivers but i dont know how to install them
i have attached a LSMOD from the q88 rom
thanks for your help
the g sensor works aswell on the q88 rom
thanks
help
can any one tell me how to find out what driver does what from the LSMOD picture
if i find them
can i just add the driver to C:\Users\user\Desktop\update\system\lib\modules in the cyanongen rom
then change init.d touchscreen file C:\Users\user\Desktop\update\system\etc\init.d/07touchscreen
to the drivers added so that they load?
does each item (touchscreen, hardwarebuttons, camera etc etc) have 1 driver or do they all have multiple?
markjamieson2005 said:
can any one tell me how to find out what driver does what from the LSMOD picture
if i find them
can i just add the driver to C:\Users\user\Desktop\update\system\lib\modules in the cyanongen rom
then change init.d touchscreen file C:\Users\user\Desktop\update\system\etc\init.d/07touchscreen
to the drivers added so that they load?
does each item (touchscreen, hardwarebuttons, camera etc etc) have 1 driver or do they all have multiple?
Click to expand...
Click to collapse
hi as far as i know there is no way to find out what driver is for what piece of hardware... although normally you can just make educated guesses from experience by looking at the lsmod screenshot from your first post your touchscreen driver is mxc622x BUT if your ts currently does not work then this is the wrongly loaded driver and you need to change this to get the ts working (trial an error)... and as for doing what you describe above i am not sure this will work although i have never tried your method using init.d??
have a read through my other thread an you will see how i do it >>> http://forum.xda-developers.com/showthread.php?t=2189569
managed to get cyangen working with the touchscreen, was a total nightmare installed wrong cwm n could not mount storage, managed to install correct one after i found out how many partitions i had, after i got cyanogenmod loaded without touch screen then ext-sd got corrupt and wouldnt mount so i had to wait for a card reader to format it, after i got everything working that i needed the internal sd went corrupt, i had to mount it using CMW then full format it.
ive got fpse workin great, its overclocked 1200mhz normal use but 1100mhz with fpse, i also use a app called touch screen digitizer booster which works great aswell, its a great tablet for £45 considering i only use it for fpse, my only problem is cant charge while using otg, might try a few bluetooth dongles
the voluume buttons and camera dont work but i never use them
cheers
Hi
I'm trying to port sense 6 (TRYING ) from M8 to Sensation. I took as base CM11 and as port stock system from M8. Copied framework, apps, priv-apps, media, fonts, some libs etc. First boot gave me this log (ofc bootloop, looping this log):
http://pastebin.com/NAt0PL4D
Then I disabled starting media server, which gave me this:
http://pastebin.com/wjDE31Ww
I tried to replace libs and bins mentioned in this logcat, but no success. Could someone help me with finding reason of this loop?
Thanks in advance!
Hi everybody,
I compiled my own CM-11 for my Galaxy Tab 2 10.1 (P5110) following this guide and got the following issue.
It is not possible to switch on the WLAN. When I move the switch to 'On' no WLANs are shown and it says "To see available networks, turn Wi-Fi on" that's it?
For testing purposes I've installed cm-11-20160320-NIGHTLY-p5110, there Wlan is working.
Any ideas or hints to figure out what's wrong?
Regards Pete
Cause I suspected missing drivers, I've adapted the script 'extract-files.sh' to pull the proprietary files out of the ROM mentioned above.
Thereafter I recompiled my ROM, but Wifi is still not working. The output of logcat and dmesg is attached.
Thanks for any help!
Regards Pete
...I'm a step further.
To have the same conditions as in the nightly, i build a ROM with the 'build_manifest.xml' out of the nightly. After a comparison of both, I've found out that in my ROM in the directory '/system/etc/wifi' the following files are missing:
Code:
bcmdhd_p2p.bin
nvram_mfg.txt
nvram_net.txt
I've copied these files from the 'nightly' to my ROM and guess what... WLAN is working now!
But there's still one question left, why aren't these files compiled with my ROM?
Does anybody know the answer for this?
Regards
Pete