Related
If u want to store more than one android build in ur SD card u just have to make folders and put the build in there.example:
u want the gingerbread 2.3.1 bulld and the FRX04 build in your sd card
make a folder in ur SD named BUILDS(or anything that u want)
in this make a folder named ginger(for tha 2.3.1 build) and one frx04(for tha xdadroid frx04)
then edit the startup.txt from each built.add "rel_path=BUILDS/ginger"to the gingerbread build and "rel_path=BUILDS/frx04" for the frx04
"rel_path=xxx" this command changes the boot folder
Hmmmm...good....then how to choose it?? When we use GenY Dual Boot.
Sent from my SuperFroyo by Neopeek using XDA App
i think that tou have to change the registry....look at this(http://forum.xda-developers.com/showthread.php?t=623792)i personaly don't use bual boot....just run haret.exe manualy...
thanks. Do we use the same Haret.exe + intrd + etc. for all builds ? i mean, they still stay in the root of the SD card right ?
working with two neopeek builds
Working with two neopeek builds in etx2 install?
Regards
morocomolr said:
Working with two neopeek builds in etx2 install?
Regards
Click to expand...
Click to collapse
I Think it work!
When you edit startup.txt root=/dev/mmcblk0p3, it will...??
nice info!
thanks! ^_^
Multiple ext2 builds needs editing init file
morocomolr said:
Working with two neopeek builds in etx2 install?
Regards
Click to expand...
Click to collapse
As far as I know, it needs editing of at least the init file at root.
Maybe an experienced user can confirm that.
I have had success at booting multiple ext2 installs, but it is very buggy for me.
Just started looking at Android.
Requirements:
Build #8 and higher: Clockworkmod Recovery 3.0.0.7 or higher is REQUIRED!
You don't have 3.0.0.7 or higher installed I cannot help you out with any issues as these scripts do not play nicely with anything earlier than 3.0.0.7!
You have been warned!
How To Install:
Coming from another ROM or doing a clean install:
Step 1: NANDroid first!
Step 2: Do a full wipe! This means format everything!
Step 3: Flash desired build, wait for install to finish and reboot
Step 4: Enjoy!
Upgrading from nightly #X or ProTekk build #Y using build #8 or higher:
Step 1: NANDroid first!
Step 2: Flash desired build, Dalvik and cache will be wiped automatically!
Step 3: Enjoy!
Google Applications (GApps):
http://goo-inside.me/gapps/
CyanogenMod changelog & merges:
http://review.cyanogenmod.com/#q,status:merged,n,z
Stock Build Download Locations:
http://www.mediafire.com/cm7/inc
Experimental Build Download Locations: Abandoned for now until I have more time/help
http://www.mediafire.com/?8z38p1pgyag72
Experimental Builds With Custom Kernels:
Included kernels:
Incredikernel from 03/06/11
Invisiblek from 03/09/11
SavagedZen no SBC
Tiamat from 03/05/11
Please remember that they are experimental!
With these, ALWAYS wipe Dalvik and cache! No longer needed as it is auto wiped - Build #8 and higher!
Updates:
Experimental builds #8 & stock #8 released @ 00:14 AM EST 03/12/11
Experimental builds #7 & stock #7 released @ 7:30 AM EST 03/11/11
Experimental builds #6 released @ 1:05 PM EST 03/10/11
Experimental Build #5 With Custom Kernels released @ 1:33 PM EST 03/09/11
Build #5 released @ 10:12 AM EST 03/09/11
Build #4 released @ 2:50 PM EST 03/08/11
Build #3 released @ 9 AM EST 03/08/11
Build #2 released 03/06/11
Build #1 released 03/06/11
To-Do List:
Automatically wipe Dalvik and cache prior to installing. Abandoned for the moment. Working properly!
Credits:
CyanogenMod Team for the incredible ROM they've given us
Slayher for many many many fixes and guiding me here and there! Thanks!
Calkulin for his format script - Thank you!!!!!
NilsP for helping me out with the format script
Chad, Invisiblek, SavagedZen team, and Cayniarb for your amazing kernels
If I have forgotten anyone I'm sorry! Let me know and I'll give you credit!
Q: What is this?
A: This is something I have started doing since the buildbot has been on hiatus and I needed to feed my addiction to flashing the most recent build of CyanogenMod 7 I could get my hands on.
I started doing this for myself and saw that there was a pretty big demand for the newest updates possible so I said why not share it with everyone.
Nothing in my builds have been altered so don't worry. It is not a ROM I have customized. All I am simply doing is pulling the source every morning and compiling it.
Q: Wait, so this is the same as the CyanogenMod 7 nightly builds? Why rename it and make it?
A: Great question. Think about it this way. The CyanogenMod team builds nightly right? Well, lately it hasn't been nightly but more random. The advantage of building daily, for me and the people on the east coast, it is much better to have a new build readily available in the morning versus waiting all night for a release or no release at all and wasting time. I am not taking credit for the CyanogenMod team's work and I refuse to as I am simply pulling the source and compiling it. The renaming of my builds is to defer the confusion between the CyanogenMod nightly builds as my builds have nothing to do with how CyanogenMod builds and releases.
Q: Ok, so if I am having issue X,Y,Z who do I report it to?
A: If it is a known issue please post it in the RC 1.5 thread. If it is an issue that is not known and has started with one of my builds please report it here via a post or a PM and I will be more than happy to help out and see if I can fix it.
Q: Uh, if there are nightlies then why would I want to use your builds? Doesn't it make sense to use one of the nightlies?
A: Sure, you are more than free to use one of the official CyanogenMod nightlies! The reason why some use my builds is simply the fact that they want to have the newest updates and merges on their device! The buildbot does not always pump out a new nightly where as I always will be building and compiling every day. Also, the nightlies don't always include the newest merges because of the fact that merges can be push at any time.
Q: If you are building these daily what happens if updates are merged after you build?
A: Haha, I know this is sad but I don't have much of a life but I do have one! I keep on top of all the merges almost like clockwork! I normally check about every hour to see if there are any major updates and fixes. If a major fix is merged I will be pushing out another build as soon as I see that it has been merged! So no need to worry about having the newest build besides downloading it and installing it.
Q: Ok, so nightly #X is released, wouldn't it be the same as your build #Y?
A: This is a little harder to answer but I will make it simple. As I said before and as many have noticed, the buildbot doesn't always push a new build. For example, my builds #1 and #2 are the same as nightly #13. RC 2 and nightly #14 were released and both are just about the same from CyanogenMod. My build #3 includes the new merges after both of those have been built so mine would be newer. I will be working on a log that tracks the differences between the nightlies and my builds shortly.
Q: What's the deal with the kernels? Why are there the same number build but different names?
A: I have noticed that everyone has their own "go-to kernel" after they flash a ROM. I have collected the top 4 gingerbread kernels used and incorporated them into each build I do. There is the stock build which is nothing different than what the CyanogeMod team puts out, Incredikernel, Invisiblek, Tiamat, and SalvagedZen. You can choose whatever one you want to use. The purpose of this is to simplify the install process for the user so that there is no need to be flashing multiple zips just because you're updating to the newest build.
Q: I can't get CWM 3.0.0.x to update on my phone. I don't know what I'm doing wrong. Every time I go to recovery, it says i'm running 3.0.0.x
A: ROM Manager > Menu > Settings > Erase Recovery > Back > All ClockworkMod Recoveries > select 3.0.0.7 or higher
Any other questions? Please let me know and I will include them in this post!
------------------------------------------------------------------------------------------
I personally test out each build as I release them and if there is one posing serious issues I will pull it from my site!
I have successfully used the stock kernel, incredikernel, and Tiamat on my builds without issues.
All my builds will be online and ready to download no later than 10 AM eastern time! I try to get them out as quick as possible for you guys!
As a sidenote and fore more clarification, I am NOT taking credit for the fabulous work that the CyanogenMod team is doing! This is NOT a custom ROM I have edited or made! This is always going to be straight from the CyanogenMod team's source!
I will be doing this past RC 2 and if CyanogenMod 7 gets release as a stable build and solidified I will be building as long as there are updates merged!
Please enjoy it and happy crackflashing to all!
This is great, now I don't have to scroll through the other thread for your builds, thanks Protekk
Sent from my ADR6300 using XDA App
nerogold said:
This is great, now I don't have to scroll through the other thread for your builds, thanks Protekk
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Not a problem! I aim to please!
So what are the "fixes" you mentioned in the other thread that you merged at 9AM? I am doing a fresh install of RC2 because I have been wanting to use one of these themes since RC1, but he doesn't update it for nightlys...
If the fixes aren't anything huge then I will try to stick with RC2 for atleast half a day
GatorsUF said:
So what are the "fixes" you mentioned in the other thread that you merged at 9AM? I am doing a fresh install of RC2 because I have been wanting to use one of these themes since RC1, but he doesn't update it for nightlys...
If the fixes aren't anything huge then I will try to stick with RC2 for atleast half a day
Click to expand...
Click to collapse
If you visit the link to the merged changelog, anything that is there before 9 AM easter time is in this build. This includes a major fix for people having bootloop issues with RC 2. My build #3 can be considered RC 2 + fixes.
So far build #3 seems to be working with the RC2 DTR!
That's good to hear Derrty!
No more SD card damaged with #3, thanks for compiling !!! Now I can decide if I want to try the new kernel from Chad.
The one thing I learned from all this is that it's good to have a backup SD card that has restores on it. That way when your SD card gets F#[email protected]#$ up, you can just put in your other SD card and your up and running.
I have a complete backup of the SD card on my pc
dspcap said:
No more SD card damaged with #3, thanks for compiling !!! Now I can decide if I want to try the new kernel from Chad.
The one thing I learned from all this is that it's good to have a backup SD card that has restores on it. That way when your SD card gets F#[email protected]#$ up, you can just put in your other SD card and your up and running.
Click to expand...
Click to collapse
yeah it is. but it sucks when you have 32gig card and 28gig's are used and you have only usb 1 with a 1.25mb transfer speed.... :'(
cd2573 said:
I have a complete backup of the SD card on my pc
Click to expand...
Click to collapse
but it changes constantly with your apps too. it would be very time conduming to do it everyday
Mozy has a new mobile app coming that will automatically backup your phone.... not sure how it will work, but quite interested.
v941726 said:
but it changes constantly with your apps too. it would be very time consuming to do it everyday
Click to expand...
Click to collapse
Take a look at rsync backup for Android. rsync is my favorite tool for backups since it only copies the changes to the files in question (even large files that are modified but largely the same - rsync only copies the changes). I use that app, combined with Tasker to automate a nightly backup of my sd card as well as instant backup of my dcim dir. when the camera app exits. Oh and to sync podcasts to my phone from my mac. If you're running linux or OSX you've got rsync native on your system (just be careful learning how to use it so you don't clobber any important files). If you're on windows, there are some implementations of rsync (here's one) but I've never tried 'em so I dunno how well they work...
Yeaaaaaa! No more damaged sdcard! Thanks dude!
Sent from my ADR6300 using XDA App
wildland said:
Take a look at rsync backup for Android. rsync is my favorite tool for backups since it only copies the changes to the files in question (even large files that are modified but largely the same - rsync only copies the changes). I use that app, combined with Tasker to automate a nightly backup of my sd card as well as instant backup of my dcim dir. when the camera app exits. Oh and to sync podcasts to my phone from my mac. If you're running linux or OSX you've got rsync native on your system (just be careful learning how to use it so you don't clobber any important files). If you're on windows, there are some implementations of rsync (here's one) but I've never tried 'em so I dunno how well they work...
Click to expand...
Click to collapse
thanks. i've been looking for something like that. using tasker and getting it to work the way you want is more of a chore sometimes though
ProTekk Build #4 on its way. Including the merges from this afternoon.
man you are not playing
cd2573 said:
man you are not playing
Click to expand...
Click to collapse
Not one bit. I'm staying true to my word. I promised the community this so I'm going to do it! Even though the woman is getting annoyed by this I'm still doing it
Update: ETA 10 minutes until completion and +5 for uploading. Get ready!
Update #2: Uploaded and ready on my site! Link is in the first post!
Mediafire link is up as well.
I love how fast these are coming.
It appears they have released an official Alpha for the Samsung Tab 7510, WiFi only. I don't know how this compares to the AOKP versions of ICS that have been released, that to my knowledge are based upon CM9.
For anyone interested, the download is here:
http://android.chemlab.org/snapshots/p4wifi/
Also, here's a small thread on the release. Also, there might be a better download from Rootzwiki, in that there could be kernel issues with the CM version. Obviously, install any of these versions at your own risk.
https://plus.google.com/100275307499530023476/posts/1Lm5iULvf3w
Skilover said:
It appears they have released an official Alpha for the Samsung Tab 7510, WiFi only. I don't know how this compares to the AOKP versions of ICS that have been released, that to my knowledge are based upon CM9.
For anyone interested, the download is here:
http://android.chemlab.org/snapshots/p4wifi/
Also, here's a small thread on the release. Also, there might be a better download from Rootzwiki, in that there could be kernel issues with the CM version. Obviously, install any of these versions at your own risk.
https://plus.google.com/100275307499530023476/posts/1Lm5iULvf3w
Click to expand...
Click to collapse
Yup - already a thread in the general section. Has a link to a CWM flashable version
The official Alpha is great Running it at the moment!
what time release for galaxy tab 3G-wifi ??
you don't say
What's the diff better this and are kangs
Sent from my SGH-I777 using xda premium
There shouldn't be any difference code is code so the one from rootz wiki is the same I believe though I read the latest kernel has issues with wifi not sure
Sent from my Nexus S using XDA App
nandihno said:
There shouldn't be any difference code is code so the one from rootz wiki is the same I believe though I read the latest kernel has issues with wifi not sure
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
The issue seems to be the kernel, and the Kang fixes it. My question is, are the AOKP releases we are using here also based on the same code, or is this newer code? Has anyone compared this "official build" or the kang that fixes the kernel, versus the kangs like aokp? I wonder if they have been getting builds from CWM all along, or if they are based upon older builds than this alpha release?
Is it possible to just flash the update cm 9 zip file using cwm v5.0.2.7?
Damien Hede said:
Is it possible to just flash the update cm 9 zip file using cwm v5.0.2.7?
Click to expand...
Click to collapse
Yes it is possible. I had to go into the zip at location
update-cm-9-02192012-SNAPSHOT-p4wifi-signed.zip\META-INF\com\google\android
open the file updater-script with notepad and delete the first line which begins with assert. Save the file back to the zip and flash.
Bratag said:
Yup - already a thread in the general section. Has a link to a CWM flashable version
Click to expand...
Click to collapse
Can you tell us where that version is? I tried searching the General forum and can't find anything.
---------- Post added at 12:50 PM ---------- Previous post was at 12:30 PM ----------
mystery_tx_man said:
Yes it is possible. I had to go into the zip at location
update-cm-9-02192012-SNAPSHOT-p4wifi-signed.zip\META-INF\com\google\android
open the file updater-script with notepad and delete the first line which begins with assert. Save the file back to the zip and flash.
Click to expand...
Click to collapse
so basically take out this entire line here? Where do you end the line at?
assert(getprop("ro.product.device") == "p4wifi" ||
Exactly what I did......testing now. You are going to need the Google apps CWM zip though. No market and whatnot!
so basically take out this entire line here? Where do you end the line at?
assert(getprop("ro.product.device") == "p4wifi" ||[/QUOTE]
You can place a # sign at the beginning of that line and save it.
I use notepad++. I am not sure if notepad formats it correctly.
If you use the Kang version on the OP, you don't have to do this--I installed that using CWM 4.0.0.4, no problems, without having to edit anything--Patrick did it for us.
mystery_tx_man said:
so basically take out this entire line here? Where do you end the line at?
assert(getprop("ro.product.device") == "p4wifi" ||
You can place a # sign at the beginning of that line and save it.
I use notepad++. I am not sure if notepad formats it correctly.
Click to expand...
Click to collapse
It won't. Notepad uses \x0d \x0a endings; Notepad++ can use \x0d \x0a [Windows/DOS] line endings, \x0d endings (Unix), and \x0a (Mac) endings, and uses the current one (in this case, Unix) by default. That file must use Unix endings.
[ASCII 101, if needed: \x0d = Carriage Return, \x0a = Line Feed]
https://plus.google.com/115013390614274076135/posts
Hopefully some up-to-date news.
OpenPDroid is an awesome mod developed and maintained by CollegeDev, FFU5y, Mateor, Pastime1971, Syvat and Wbedard that allows you to configure for each app separately exactly which permissions it should have and block or spoof everything else. Unfortunately, it can only be used if the core platform is integrated directly into the ROM. (For more details, see http://forum.xda-developers.com/showthread.php?t=2098156)
Since I have completed the integration anyway during my attempts to fix the HDMI rotation bug (without success so far, I'm afraid) and the current version of CM does not seem to contain any more critical bugs, I thought others might like to make use of my ROM as well.
I therefore hereby present: CM 10.1 with OpenPDroid integration. Besides the platform integration I made the following changes:
PDroid Manager app integration.
Standard CM Updates are disabled by default.
CM anonymous stats collection is disabled by default.
Google Analytics integration has been removed from the CM stats collection module.
Updates and anonymous stats collection can simply be enabled again using the menu. (Warning! Applying a normal CM update purges the OpenPDroid integration!)
I will try to at least provide updates to newer versions at critical update moments and will perhaps provide some more in between.
You'll need to have ClockworkMOD installed in order to flash this ROM.
Downloads:
11/07/13: Version based on CM 10.1.1 stable. Steps:
1. Flash the stable version of CM 10.1.1 (10/07/13) for our device.
2. Flash this OpenPDroid patch.
3. Install PDroid Manager either from the Play Store or using the APK attached to this post.
10/07/13: (based on source code 09/07)
10/07/13: https://mega.co.nz/#!uswGGQ6K!Wt9JAFDBElZQ2i74yNxMrkz3y7kO4U8-LWK2dLx_L8s
10/07/13: MD5: 99fc3769c9b2354a844ac1ac92504650
16/05/13: (build with standard CM kernel)
16/05/13: https://mega.co.nz/#!StIyQbzD!GfgNa3Seha74UnSahokwIzvcZ9UVqKaa2P38_LlxuMY
16/05/13: MD5: ad036e4035291bba901ad90826ab0abf
13/05/13: (general source code cleanup)
13/05/13: https://mega.co.nz/#!KoxixajK!Wn91VGj5ooOFYXs-Vt8QJDkU8Bo7VuR40_939hd3YMg
13/05/13: MD5: dffad528804bf830c4b225b0bfff5a76
09/05/13: (WerewolfJB kernel v003 new)
09/05/13: https://mega.co.nz/#!2txwmS4S!aR4bHG6BHMkoTPabi8Z0K0r4hPsUICmKO9ROaaIYOg0
09/05/13: MD5: 4a75829296a167a563ad78ffe26991de
05/05/13: (vibration,memory management)
05/05/13: https://mega.co.nz/#!bsQERDaS!RHB4rHhQsDf9XauyOpeMySAiDt1gtc8Y7gnsckdWOlo
05/05/13: MD5: e05017acf9e50affcba7379050514d63
01/05/13: (merged in the WerewolfJB kernel, fixed headphone button actions)
01/05/13: https://mega.co.nz/#!ig5hCJYY!eHM5vwER9zEEZJRk9_C6vCvclH14rDcKa9CyBcU9kTc
01/05/13: MD5: 3ababb1c0cda47874ed7d688de032638
28/04/13 (adjusted some device references for improved custom recovery compatibility)
28/04/13: https://mega.co.nz/#!71BgVLBY!PEcEHAYxpDZVZcQycpgGJ2QeJZZ0HbgVdjaBkiD72bg
28/04/13: MD5: 7f2616736dd78940e37d1e14ea47084f
24/04/13: (storage, power profiles)
24/04/13: https://mega.co.nz/#!j44XWBDb!UrmGEhCUcjbj8Q3WTj1EkDrImXJXwcNGvEMIHFm-TvE
24/04/13: MD5: 491a500c5bef958d7575a6ce62fae1aa
23/04/13: https://mega.co.nz/#!75IDhCAA!EpwDqHm6W6fG3mk0lNaC0XPWvlsJxi2TjEpjJPEuj6Q
23/04/13: MD5: 609c76958796f19fb04aee217c44ba98
PS. If anyone ever discovers the correct procedure for calling the proprietary nvidia tegra driver api, please let me know.
is the baseband wakelock solved in this rom?
Who can change the other network disk ，thx
xtribas said:
is the baseband wakelock solved in this rom?
Click to expand...
Click to collapse
The main additional problem that this ROM currently fixes compared to standard CM is that of blatant privacy violation.
Since the wakelock issue seems to be related to mobile data use, and I don't have a data subscription, experimentation with this would quickly rack up my phone bill. If someone comes up with a solution I'd be happy to patch it out though.
Hansey said:
Who can change the other network disk ，thx
Click to expand...
Click to collapse
I assume you're referring here to the swapping of disk names when using MTP. I actually only noticed this bug last night and it should be easy to fix. I plan to have it patched out in the next version.
Update 24/04/13 uploaded, involving official CM patches for MTP storage & power profile settings.
Is there a guide how to compile it my self?
DavidXanatos said:
Is there a guide how to compile it my self?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1994860
DavidXanatos said:
Is there a guide how to compile it my self?
Click to expand...
Click to collapse
At the Cyanogenmod website there are instructions for compiling yourself. You can apply the OpenDroid patches using the link I included in the post. Make sure to synchronize the proprietary files with those provided by Cyanogenmod or some aspects will fail to work.
@Wenque - As the original CM on which you based this has the incorrectly labelled hardware platform which means it can only be flashed with the one particular version of CWM, could you possibly modify your version so the coding is for X3, not for P880 - then it could be flashed with any recovery.
SimonTS said:
@Wenque - As the original CM on which you based this has the incorrectly labelled hardware platform which means it can only be flashed with the one particular version of CWM, could you possibly modify your version so the coding is for X3, not for P880 - then it could be flashed with any recovery.
Click to expand...
Click to collapse
Thanks for pointing this out, as I wasn't aware that my ROMs still suffered from this problem. I'll look into it.
Wenque said:
Thanks for pointing this out, as I wasn't aware that my ROMs still suffered from this problem. I'll look into it.
Click to expand...
Click to collapse
No problem. I got the 'Status 7' message when I tried to flash it, due to the P880.
This problem goes away with the latest (v6.0.3.1) version of CWM, so it's not massively important I guess. It would be better if CM modified their builds to reflect the correct hardware identifier.
May be worth you expanding your OP slightly to contain a link to the correct CWM - just to make it easier for people to find.
SimonTS said:
No problem. I got the 'Status 7' message when I tried to flash it, due to the P880.
This problem goes away with the latest (v6.0.3.1) version of CWM, so it's not massively important I guess. It would be better if CM modified their builds to reflect the correct hardware identifier.
May be worth you expanding your OP slightly to contain a link to the correct CWM - just to make it easier for people to find.
Click to expand...
Click to collapse
Good idea. I'll probably just expand the model check in the update script for future uploads so it accepts both references.
Update 28/04/13 uploaded, for some improved custom recovery compatibility. As every update, it also contains all official CM patches.
All patches between this version and the last one are minor, so for people who have installed the previous version of the ROM there is no need to update to this one.
Is anyone else having problems with GPS on this ROM? I am going to try going back to all the old methods I used on my HTC DesireS, but thought I'd ask here as well.
For those who wonder what the old methods were, have a look at derekgordon.com
SimonTS said:
Is anyone else having problems with GPS on this ROM? I am going to try going back to all the old methods I used on my HTC DesireS, but thought I'd ask here as well.
For those who wonder what the old methods were, have a look at derekgordon.com
Click to expand...
Click to collapse
No-body?
I have tried ths both with Derek Gordon's gps.conf modification, and with my own one using just the UK NTP servers and no fancy settings.
If I reboot the phone and run GPS Status & Toolbox it takes between 3 and 5 minutes to get the first lock. This happens whether I do it immediately on reboot or leave the phone alone for an hour first. Once it has established a first good lock, GPS seems to be very good - relocks quickly and stays in the background happily.
The problem is the first lock - it's almost as if the hardware is actually starting off disabled and takes time to warm up or something.
Can someone else using this ROM please test to confirm? I will try this with the standard CM 10.1 build and also with the Stock ROM again, but can't do so for a couple of days.
Update 01/05/13 uploaded. I swapped the default CM kernel with the WerewolfJB kernel (thanks laufersteppenwolf!) and I fixed the headphone button actions (key 248 HEADSETHOOK).
SimonTS said:
Is anyone else having problems with GPS on this ROM? I am going to try going back to all the old methods I used on my HTC DesireS, but thought I'd ask here as well.
For those who wonder what the old methods were, have a look at derekgordon.com
Click to expand...
Click to collapse
Sorry SimonTS, but I don't know whether this version fixes your GPS problems. Perhaps I'll have time to look into it later.
Wenque said:
Update 01/05/13 uploaded. I swapped the default CM kernel with the WerewolfJB kernel (thanks laufersteppenwolf!) and I fixed the headphone button actions (key 248 HEADSETHOOK).
Sorry SimonTS, but I don't know whether this version fixes your GPS problems. Perhaps I'll have time to look into it later.
Click to expand...
Click to collapse
No need to apologise mate. I have tried the WerewolfJB kernel, but it doesn't seem to make any difference. I'm going to look at running the WerewolfJB ROM for a while as GPS seems to work perfectly in that, but hopefully you will get time to build a new version as I really want a ROM with pDroid in it.
SimonTS said:
No need to apologise mate. I have tried the WerewolfJB kernel, but it doesn't seem to make any difference. I'm going to look at running the WerewolfJB ROM for a while as GPS seems to work perfectly in that, but hopefully you will get time to build a new version as I really want a ROM with pDroid in it.
Click to expand...
Click to collapse
All you really need to do is copy the good /system/etc/gps.conf file to the PDroid ROM and make sure that you do not block too many permissions. You are probably using Google's SUPL server to help you obtain an initial location estimation and you don't want to block that if you rely on fast GPS locks.
You can do this by first copying the gps.conf file to a safe location (root of sdcard for instance in /mnt/shell/emulated/) and then performing the following steps:
- Use the terminal emulator with the following commands:
= su
= mount -o remount,rw /system
- Now copy the good gps.config file over the current one (for instance using root-permission File Manager or 'su', 'cp /mnt/shell/emulated/gps.conf /system/etc/' )
- Either reboot now or use the terminal emulator with the following commands:
= su
= mount -o remount,ro /system
Wenque said:
All you really need to do is copy the good /system/etc/gps.conf file to the PDroid ROM and make sure that you do not block too many permissions. You are probably using Google's SUPL server to help you obtain an initial location estimation and you don't want to block that if you rely on fast GPS locks.
You can do this by first copying the gps.conf file to a safe location (root of sdcard for instance in /mnt/shell/emulated/) and then performing the following steps:
- Use the terminal emulator with the following commands:
= su
= mount -o remount,rw /system
- Now copy the good gps.config file over the current one (for instance using root-permission File Manager or 'su', 'cp /mnt/shell/emulated/gps.conf /system/etc/' )
- Either reboot now or use the terminal emulator with the following commands:
= su
= mount -o remount,ro /system
Click to expand...
Click to collapse
It's not that simple mate, but thanks for the reply. I know all about the gps.conf file as we used to have real problems with GPS on my old Desire S. The problem I see with this build and the standard CM is almost as if it doesn't know how to talk to the GPS hardware properly.
With the WerewolfJB build and my own gps.conf file I can get a lock in under 10 seconds sometimes, and always under 20.
A. Why change RIL?
Hey, everyone.
As a user that's been using custom roms since our bootloader was unlocked, I'm aware that some of us have some issue with telephony & mobile data (in short, RIL) - occasionally IMEI wouldn't be read on boot, which would lead to device not being registred on network. Sometimes, the network would "die" in a way - you'd get an error when trying to dial a number, and when someone would call you, they'll hear the ringing tone while your cell phone would not ring at all.
The cause of the problem seems to be some lazy coding by official CM developers/maintainers for our device. This was picked up by a developer named kholk, so he did his best to recode it properly, however it was never included into official CM device tree for reasons unknown to me (more info about the issue can be found here: http://review.cyanogenmod.org/#/c/47980/).
Kholk did include his own custom RIL into his EPRJ roms, but the roms are kinda old and have iffy baseband (which seems to be kernel issue, as he's using his own, 3.4 kernel instead of CM's 3.1 kernel in other custom roms).
So, with the help of Adam77Root, I've learned a way on how to implement EPRJ RIL into other custom roms (since I still had RIL issue with default CM RIL in 4.3 roms even) - so far I've tested it with Vanir 4.3, Carbon 4.3, Carbon 4.3.1, and few 4.2.2 roms, and I havent had ANY issues I had in CM RIL.
So, this is a tutorial to show you how you can import EPRJ RIL to any custom rom you'd like, in case you have issues with cell connection.
-this should work on any kernel and any custom rom (4.2.2+)! Tested so far, as far as kernel goes, are iodak 8/8.5, WWJB8/8b, Optimus Prime several versions, Optimus Play! 2.53.
-KK roms tested are P.A. by @dcos which has eprj ril by default, official CM nightlies and several others
-some KK roms, for some reason, don't have x3ril.smali file in their telephony-common.jar. To implement EPRJ RIL in these roms, follow the tutorial up to point 5, and skip that one, since you don't have anything to delete. After point 13, you need to do one additional thing - you need to edit ROM's build.prop settings, look for this line: "#ro.telephony.ril_class=X3RIL", and delete "#" so this line would be included in build.prop. After that, you're ready to flash. Thanks goes to @gerciolisz for the tip on the build.prop settings.
-/As of 24.01.2014. i've added another zip file which contains x3ril.smali taken from P.A. port by dcos - i'd recommend using this one for 4.4.2 roms/
-as of 11.06.2014., I've added x3ril.smali (it's in omni-v1.rar) made by adam, which is based on omni's RIL but has eprj RIL recovery. if you're on 4.4.3 kitkat rom and have issues, i suggest you give this file a try first before others
B. What's needed?
First off, you'll need a few things:
- Android Multitool from http://forum.xda-developers.com/showthread.php?t=2326604, many thanks to @Flextrick
- Read the linked topic - it's the instruction on how to use it, and in case you encounter any errors, that's the place to search for solutions
- Attached is a RAR with two files in it, X3RIL_old.smali and X3RIL_new.smali. You need only one of those - but more info about them will be in the other steps.
- Custom ROM you want to edit
- Common sense
- WinRAR & JAVA
C. How to change RIL?
Steps:
1. First step is to open the .zip of your custom ROM you want to edit, and search for system/framework/telephony-common.jar
2. Extract it to AndroidMultitool/Files, and after extract is done, delete it from .zip
3. Open Android Multitool, under Decompiling select .jar, then select telephony-common.jar in AndroidMultitool/Files, click "decompile"
4. After you're done, check if there were any errors in the Log, in AndroidMultitool main window
5. Head over to AndroidMultitool/Decompiled_jar/telephony-common/com/android/internal/telephony and look for X3RIL.smali. This is CM's RIL implemented in custom roms, which we dont need anymore, so delete it
6. Now, you need to decide wether to use X3RIL_old.smali, which is RIL from EPRJ CM10.2 built on 20130813, or X3RIL_new.smali which is RIL from EPRJ CM10.2 built on 20131007. I'm using 20131007 atm, and it's working without issues
7. When you've decided, move it back into AndroidMultitool/Decompiled_jar/telephony-common/com/android/internal/telephony and rename it to X3RIL.smali
8. Back in AndroidMultitool, under Compilin, select jar, and for folder select AndroidMultitool/Decompiled_jar/telephony-common, press "compile", and check for errors in Log
9. Output should be classes.dex file under AndroidMultitool/Compiled_jar
10. Open telephony-common.jar in AndroidMultitool/Files with WinRar - you should see META-INF folder, with classes.dex file
11. Delete classes.dex file in WinRAR
12. Move classes.dex file from AndroidMultitool/Compiled_jar to telephony-common.jar opened in WinRAR
13. Paste telephony-common.jar into system/framework inside the custom rom .zip file
14. You now have modified ROM ready to flash on our device!
D. Thank You's
Thank you's go out to @kholk for his RIL programming, @dcos for first implementing EPRJ RIL into a rom (his P.A. unofficial port for our device) different than EPRJCM10.2, @Adam77Root for his tutorial that I basically beutified and made sure is easier to understand & his modification of x3ril.smali from omni, @gerciolisz for the tip about build.prop settings, @Flextrick for his Multitool with neat GUI to extract .jar files, and all the other devs of p880 making our device worth every dime I've spent on it.
Flying_Bear said:
Kholk did include his own custom RIL into his EPRJ roms, but the roms are kinda old and have iffy baseband (which seems to be kernel issue, as he's using his own, 3.4 kernel instead of CM's 3.1 kernel in other custom roms).
Click to expand...
Click to collapse
Dude, i think you missed out the clarification for the users on whether or not they need to use the EPRJ Kernel and if anykernel will still work or normal kernels will work etc. Because your bound to have the first person to ask a question will either be, "How do i declare java paths" and "Will 'kernel name here' work with it", this isnt me asking, more of an fyi post (Y)
I do apologize about it, but saves you the time and effort of answering the question every day
MOD EDIT: watch your language please.
penguin449 said:
Dude, i think you missed out the clarification for the users on whether or not they need to use the EPRJ Kernel and if anykernel will still work or normal kernels will work etc. Because your bound to have the first person to ask a question will either be, "How do i declare java paths" and "Will 'kernel name here' work with it", this isnt me asking, more of an fyi post (Y)
I do apologise about it, but saves you the time and effort of answering the question every day
Click to expand...
Click to collapse
np, thanks for the tip. i'll add in OP that it works with any kernel
MODERATOR EDIT: @penguin449 watch your language
I flashed Vanir nightly 171013 with Optimus Prime 2.70 kernel and telephony was completely disabled. I was not able to find or register to the mobile network. I tried modifying the RIL file as explained in this post; initially with the "new" file which didn't seem to solve the problem (still didn't get signal) but I didn't wait I immediately tried flashing the ROM with the "old" RIL instead. Initially there was no signal although I was able to find networks, but after a reboot the phone finally managed to connect to the mobile network.
I'm not sure whether it would've worked after a reboot with the "new" but I'm guessing if it's working with the "old" RIL I got nothing to worry about right?
Vanir is 4.3.1 while OP is for 4.3, i think thats your problem. Different RIL would not help in that case. Flash Anykernel version of OP, or find a version repacked with 4.3.1 ramdisk. Good luck!
Flying_Bear said:
Vanir is 4.3.1 while OP is for 4.3, i think thats your problem. Different RIL would not help in that case. Flash Anykernel version of OP, or find a version repacked with 4.3.1 ramdisk. Good luck!
Click to expand...
Click to collapse
As far as I understood, the 171013 version did not have the RamDisk issue so I figured the CM10.2 version of Optimus Prime kernel should've worked correctly?
So I get it from you that if I flash the original rom with the AnyKernel version of OP it should work fine? (no need for any RIL modifications?)
Yep, anykernel versions of all our kernels xcept iodaks should work on any android version without any modifications.
Is there a way to do this with Linux?
If not, how about uploading modified telephony-common.jar for CM ROMs?
I tried just replacing the whole telephony-common.jar file but I couldn't send or receive any messages. Everything else seemed to work though.
Sent from my LG-P880 using Tapatalk
MilkyJoePD said:
Is there a way to do this with Linux?
If not, how about uploading modified telephony-common.jar for CM ROMs?
I tried just replacing the whole telephony-common.jar file but I couldn't send or receive any messages. Everything else seemed to work though.
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
not sure really, since i havent worked on linux systems.
and i dont think telephony-common.jar is universal for all roms (i might be mistaken though), so there's no use to upload it. however, if you want, upload your original telephony-common.jar file here and i'll do my best to mod it for you!
Flying_Bear said:
not sure really, since i havent worked on linux systems.
and i dont think telephony-common.jar is universal for all roms (i might be mistaken though), so there's no use to upload it. however, if you want, upload your original telephony-common.jar file here and i'll do my best to mod it for you!
Click to expand...
Click to collapse
I meant it would be a good idea to have a place to download the modified files for specific ROMs.
Here's the (unmodified) file for Vanir.
https://app.box.com/s/embcq9kuemfdkdb1qw63
Thanks.
Sent from my Optimus 4X HD using Tapatalk
MilkyJoePD said:
I meant it would be a good idea to have a place to download the modified files for specific ROMs.
Here's the (unmodified) file for Vanir.
https://app.box.com/s/embcq9kuemfdkdb1qw63
Thanks.
Sent from my Optimus 4X HD using Tapatalk
Click to expand...
Click to collapse
well, we have way too much roms for me to download each one and replace the RIL ^^
anyway, here's your modified telephony-common ^^ enjoy!
Flying_Bear said:
well, we have way too much roms for me to download each one and replace the RIL ^^
anyway, here's your modified telephony-common ^^ enjoy!
Click to expand...
Click to collapse
I suppose there is a lot.
I'll test the Vanir one and report back.
If it works then there's a start. I can send messages so it works so far. The only thing keeping me from staying on a CM ROM is the random signal loss.
Sent from my Optimus 4X HD using Tapatalk
MilkyJoePD said:
I suppose there is a lot.
I'll test the Vanir one and report back.
If it works then there's a start. I can send messages so it works so far. The only thing keeping me from staying on a CM ROM is the random signal loss.
Sent from my Optimus 4X HD using Tapatalk
Click to expand...
Click to collapse
check it out, this should fix that issue completely. and report when you have time ^^
Flying_Bear said:
check it out, this should fix that issue completely. and report when you have time ^^
Click to expand...
Click to collapse
If you want some 4.3.1 repacks done i can do them? or if you want some experience, i have the tools to swap ramdisks on windows in my signature that you could use...
In CM ROMs I get crazy data switches from 3g to E and G. Everything is good so far. Time will tell...
Sent from my Optimus 4X HD using Tapatalk
---------- Post added at 01:22 AM ---------- Previous post was at 01:08 AM ----------
penguin449 said:
If you want some 4.3.1 repacks done i can do them? or if you want some experience, i have the tools to swap ramdisks on windows in my signature that you could use...
Click to expand...
Click to collapse
If you can then that would be great. A download for each CM ROM would open up custom ROMs like never before.
Sort out the SD card/internal memory paths and stock ROMs would be not worth installing.
Sent from my Optimus 4X HD using Tapatalk
penguin449 said:
If you want some 4.3.1 repacks done i can do them? or if you want some experience, i have the tools to swap ramdisks on windows in my signature that you could use...
Click to expand...
Click to collapse
if you've got the time and the will, be my guest - however, i don't think it's quite worth it. Not many people have this issue, and those that do would be better off fixing it by themselves then downloading aged nightlies for the rom they're looking for.
MilkyJoePD said:
In CM ROMs I get crazy data switches from 3g to E and G. Everything is good so far. Time will tell...
Click to expand...
Click to collapse
hm, switches from 3g to 2g seems to show that there is a bad connection where you're at. try enabling 2g only or 3g only in custom rom options or quick tiles, most roms support it these days. that should save your battery for few more %.
Just wanted to say that since replacing the file I haven't had to reboot once to get SMS or network to work.
That's over a month, whereas I was having to reboot about every 2 days.
The G/3G switching has improved, but still more sensitive than stock.
Sent from my Optimus 4X HD using Tapatalk
hey what if.... there is no x3ril.smali?XD there is only ril.smali or many others
edit: its ok there just x3ril was missing
I'm on a odexed ROM (mokee 4.2.2 release) so I don't know what to do with classes.dex file multitool generates.It was meant to be used for deodexed telephony-common.jar files.So I tried these steps:
1_)deodex the ROM (using deodexer 4.3),
2_)implent RIL
3_)odex the ROM(using universal odexer 6.3.1) again which I failed to do as something was wrong with decompiling before odexing.This is probably happening due to deodex process.
I got bootloop after odexing the ROM.So I'm curious if there is a way to do this on an odexed jar file without having to deodex first.
I also tried to simply delete the odex & jar file and replace it with deodexed and eprj RIL implented jar file but the rest of the ROM was odexed so it gave me a bootloop.
I don't know much about these stuff, but I did my best searching for a solution and I'm out of ideas.All I want is to have an odexed rom with EPRJ RIL implented, I'd appreciate any help
ottomanhero said:
I'm on a odexed ROM (mokee 4.2.2 release) so I don't know what to do with classes.dex file multitool generates.It was meant to be used for deodexed telephony-common.jar files.So I tried these steps:
1_)deodex the ROM (using deodexer 4.3),
2_)implent RIL
3_)odex the ROM(using universal odexer 6.3.1) again which I failed to do as something was wrong with decompiling before odexing.This is probably happening due to deodex process.
I got bootloop after odexing the ROM.So I'm curious if there is a way to do this on an odexed jar file without having to deodex first.
I also tried to simply delete the odex & jar file and replace it with deodexed and eprj RIL implented jar file but the rest of the ROM was odexed so it gave me a bootloop.
I don't know much about these stuff, but I did my best searching for a solution and I'm out of ideas.All I want is to have an odexed rom with EPRJ RIL implented, I'd appreciate any help
Click to expand...
Click to collapse
unfortunately, i encountered the same issue, and it's beyond my knowledge on what to do with odexed roms. i bypassed the issue by using a nightly which came after the stable was released (not sure if there are any for mokee though)