Database Develop

Cyanogenmod 4.1.99 and Future Updates

I really hate posting questions but after searching for a while I think it warrants a question.
Will future Cyanogen Roms be flashable using the CMUpdater or is that now defunked after the issues with Google?
TrOjAn

TrOjAnUK said:
I really hate posting questions but after searching for a while I think it warrants a question.
Will future Cyanogen Roms be flashable using the CMUpdater or is that now defunked after the issues with Google?
TrOjAn
Click to expand...
Click to collapse
Cyanogen intends to implement his updates on CMUpdater. See his twitter
twitter.com/cyanogen

Cheers for that, Ill keep it on then.... was a little bit concerned as the Google issue made him change his releases..
Thanks, TrOjAn

as head of the cmupdater project, i can confirm that future roms will be available via the updater
we are just tryin to work out how to stop people from flashing the new rom on top of an old one (pre-google) and screwing up their phone coz they cant read instructions

What is the main differences between 4.0.4 and 4.1.99? I read that the google apps are no longer included so does this mean no app market, gmail....? And my cm updater shows the new 4.1.99 update. I have 4.0.4, can I just use the cm updater? Thanks

garok89 said:
as head of the cmupdater project, i can confirm that future roms will be available via the updater
we are just tryin to work out how to stop people from flashing the new rom on top of an old one (pre-google) and screwing up their phone coz they cant read instructions
Click to expand...
Click to collapse
Can't you pull the info from the build.prop file?
determine if its cyanogen or not
split the version info at the decimal using the split method from the string class
convert each of the three numbers to an int using parseint
determine if the 1st one is > 4
if true
is the second one >= 1
if true
is the third one == 11
if false
is the third one >= 9
if true
update past 4.1.9 is possible
theres many ways you can do that but thatll probably give good compatibility
those methods are available in java, so they should work on android right? i havent looked at androids api

[ROM] Cyanogenmod 10.1 with App Permission Control (unofficial)

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.

[STICKY] I9505G GE GALAXY S IV ( INDEX ) ROM's / LINKS / HOW TO THREAD

Welcome to the [STICKY] I9505G GE GALAXY S IV ( INDEX ) ROM's / LINKS / HOW TO THREAD formally the DISCUSSION GUIDE ​
This is the Official Index Roll up thread for the I9505G Google Edition Galaxy S IV. In this Index you will find helpful, links, guides, how to's and instructions for your I9505G.​
Please Post any links or helpful information in this thread or you can PM me so I can link it in the OP ( If your on the I9505/I9500 Please do NOT ASK about development for your device this is for the I9505G ONLY
(DISCLAIMER) As always I nor anyone is responsible if you cannot follow instructions in this or any other thread. We assume NO liability for bricks, loss of job, or the end of life as we know it.
GUIDES & LINKS
How to get CM 10.1 & CM 10.2 working on the I9505G
How Unlock the Bootloader for the I9505G
[OTA] OTA ZIP 4.3 for I9505G
How to Update your Baseband to get the 4.3 OTA
TOUCHWIZ Development Thread Q&A
Camera Save to SD Card for Google Edition ROM's
I9505G How to Set Device Mount Points in Android Kitchen GE S IV
4.3 SD Card Issue Fixed
How to upgrade a Stock+Root+Custom_Recovery I9505G from 4.3 to 4.4 and keep all Data​
ROOTING THREADS
How to Root 4.2, 4.3, 4.4 JB, Kit Kat I9505G
ROM's
[ROM][Linaro-4.8] XenonHD-4.4.2 Alpha 1 (5/1/14) *Truly Stable, Fast & Butter​
GOOGLE LITE EDITION 4.2.2 v.2 MFD
GOOGLE LITE EDITION 4.3 I9505GUEUBMH1 Ktoonsez Kernel
TOUCHLITE GE TOUCHWIZ ROM
[ROM] Google Edition 4.3 [Clean][Deodex][276MB]​
RECOVERY
How to install TWRP via Odin on the I9505G
TWRP for the I9505G
[BETA][RECOVERY] ClockworkMod Recovery 6.0.3.6​
[ODIN[TAR] Stock Recovery Images
MODEMS
ODIN TAR MODEMS
STOCK FIRMWARE LEAKS
Stock ODIN FIRMWARE Leaked 4.3 MFP ​
Stock ODIN FIRMWARE Leaked 4.3 MG8​
ODIN AND HEIMDAL PACKAGES​
Stock HEIMDAL 4.2.2 MFD back to Stock​
[ODIN][TAR] I9505GUEUAMFD 4.2.2 Full Rooted Restore
[ODIN][TAR] I9505GUEUBMH1 4.3 Full Rooted Restore
[ODIN][TAR] I9505UEUBMH5 4.3 Full Rooted Restore
[ODIN][TAR] I9505GUEUBMKG 4.4 Full Rooted Restore
[ODIN][TAR] I9505GUEUBML4 [4.4.2] Full Rooted Restore​
[ODIN][TAR] 4.4.3 I9505GUEUCNE3 Full Rooted Restore​
[ODIN][TAR] 4.4.4 I9505GUEUCNF3 Full Rooted Restore​

Reserved
Big Thanks to Illogic6 for being the Very 1st Person to get Touchwiz Booted to the I9505G post #31 and SamuriHL for solving the Baseband Update Issue and Chainfire
Modem Update : Due to the secure boot loader we cannot flash modems via cwm or any other custom recovery. You MUST update your firmware via Odin
Touchwiz Works with some ROM's like BareBones from the I9505 forum being successfully booted on the I9505G. TW Development is ongoing for the I9505G but with the small partition size some issues exist, and are being researched and worked out.
http://forum.xda-developers.com/showthread.php?t=2405273
11/28/2013 : KitKat initial release this week New Updated Odin Packages and ROM's please check A&D section
DONT FORGET TO THANK THE MEMBERS AND DEVS WORKING HARD ON THE I9505G DEVELOPMENT
07/21/2014: I just wanted to make a note that I still get emails and requests for help and although I am no longer doing any sort of work on the I9505G I will try to help you out if you PM me. PLEASE BIG THANK YOU TO @SamuraiHL he is really the one maintaining everything for I9505G Owners and if you have not thanked him please do. Actually without volunteering him he is your best POC for anything current. I will maintain the thread for organization now and then. ALOHA

MJHawaii said:
Reserved :good:
Click to expand...
Click to collapse
Nice to see someone do this. Hope this will build up and morph into ROM's, etc.
How is your ROM coming along?

wilbarger said:
Nice to see someone do this. Hope this will build up and morph into ROM's, etc.
How is your ROM coming along?
Click to expand...
Click to collapse
Right now just standard kitchen tweaks on 4.3 but I am trying to get the whole device mount points set up in Cygwin and I'm having trouble because when I extract everything and open up the recovery.fstab file with notepad ++ it does not show anything but 0p1 nothing for system, boot & data so I'm lost and need help
Sent from my GT-I9505G using Tapatalk 2

MJHawaii said:
Right now just standard kitchen tweaks on 4.3 but I am trying to get the whole device mount points set up in Cygwin and I'm having trouble because when I extract everything and open up the recovery.fstab file with notepad ++ it does not show anything but 0p1 nothing for system, boot & data so I'm lost and need help
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
One person you might contact is mohan_kr. He has come over to the S4 from the Skyrocket recently. Excellent at working on the ROM's. Sorry I can not be of assistance, but I am not very advanced on Android.

wilbarger said:
Nice to see someone do this. Hope this will build up and morph into ROM's, etc.
How is your ROM coming along?
Click to expand...
Click to collapse
wilbarger said:
One person you might contact is mohan_kr. He has come over to the S4 from the Skyrocket recently. Excellent at working on the ROM's. Sorry I can not be of assistance, but I am not very advanced on Android.
Click to expand...
Click to collapse
That's what this thread is for though for everyone to get together share information and collaborate.

Chahk's post about mount points and getting other CM/AOSP ROMs working on I9505G deserves its own link:
http://forum.xda-developers.com/showpost.php?p=43843048&postcount=30

MJHawaii said:
Right now just standard kitchen tweaks on 4.3 but I am trying to get the whole device mount points set up in Cygwin and I'm having trouble because when I extract everything and open up the recovery.fstab file with notepad ++ it does not show anything but 0p1 nothing for system, boot & data so I'm lost and need help
I saw Chahk post and it is helpful this is where I'm at right now read above. I did pm Chahk and a few others for help. I will work on it a little later this weekend
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
Sent from my GT-I9505G using Tapatalk 2

irishrally said:
Chahk's post about mount points and getting other CM/AOSP ROMs working on I9505G deserves its own link:
http://forum.xda-developers.com/showpost.php?p=43843048&postcount=30
Click to expand...
Click to collapse
x2
I've found that very useful. Been able to get every AOSP/CM based ROM to boot by editing the updater-script to match the correct partition.
Has anybody noticed that photos taken with the front facing camera on CM sometimes have green distortion? That was the only bug I've found. Unfortunately, that flared up my phone OCD enough to go back to the 4.3 leak.
Thanks for putting this thread together, OP!

illogic6 said:
x2
I've found that very useful. Been able to get every AOSP/CM based ROM to boot by editing the updater-script to match the correct partition.
Has anybody noticed that photos taken with the front facing camera on CM sometimes have green distortion? That was the only bug I've found. Unfortunately, that flared up my phone OCD enough to go back to the 4.3 leak.
Thanks for putting this thread together, OP!
Click to expand...
Click to collapse
Your Welcome. So I read on the other thread and I know myself and others are looking at how we can port other ROMs specifically touchwiz over to the G the partition as you know is an issue but I think with collaboration can be solved soon.
Keep it coming let's solve problems!
Sent from my GT-I9505G using Tapatalk 2

MJHawaii said:
Your Welcome. So I read on the other thread and I know myself and others are looking at how we can port other ROMs specifically touchwiz over to the G the partition as you know is an issue but I think with collaboration can be solved soon.
Keep it coming let's solve problems!
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
I took a TW ROM and edited the script for our devices. It boots, but the display never kicks on. You get the boot animation sound and it even mounts the storage on my computer.

illogic6 said:
I took a TW ROM and edited the script for our devices. It boots, but the display never kicks on. You get the boot animation sound and it even mounts the storage on my computer.
Click to expand...
Click to collapse
Wow that's great maybe you can help me with my script it sounds like your further along than some. I wonder what would cause the display bug doesn't sound like a boot issue
Sent from my GT-I9505G using Tapatalk 2

MJHawaii said:
Wow that's great maybe you can help me with my script it sounds like your further along than some. I wonder what would cause the display bug doesn't sound like a boot issue
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
Here's the ROM I was messing with. I used the "old firmware" because it was the newest one when I first looked. http://forum.xda-developers.com/showthread.php?t=2349369
I've attached my modded updater script. (You will have to remove the .txt extension. Wouldn't let me upload without it.) All I had to do was edit which /dev/block the script mounts before it copies stuff over. If I recall correctly, I only had to change the dev it flashes the boot.img to. See this post: http://forum.xda-developers.com/showpost.php?p=43843048&postcount=30
include 'standard_disclaimer.php';

illogic6 said:
Has anybody noticed that photos taken with the front facing camera on CM sometimes have green distortion?
Click to expand...
Click to collapse
I think this might be fixed in the newest CM nightly. I've took about 20 selfies with the front facing camera and haven't had distortion at all. Before I'd get it every 3 or 4 photos.
Edit: Disregard the above. The problem is back, but I'm thinking it might be the 4.3 camera zip I've been using. Hmmmmmmm......

I think I jumped the gun a bit on rooting my I9505G right when I got it. I've never successfully rooted it, but I managed to get on the 4.3 ROM with a few quirks here and there. My ultimate goal is to get Paranoid Android with halo running, but I'll have to dedicate a day to the whole process. I'll be keeping track of this thread.

illogic6 said:
Here's the ROM I was messing with. I used the "old firmware" because it was the newest one when I first looked. http://forum.xda-developers.com/showthread.php?t=2349369
I've attached my modded updater script. (You will have to remove the .txt extension. Wouldn't let me upload without it.) All I had to do was edit which /dev/block the script mounts before it copies stuff over. If I recall correctly, I only had to change the dev it flashes the boot.img to. See this post: http://forum.xda-developers.com/showpost.php?p=43843048&postcount=30
include 'standard_disclaimer.php';
Click to expand...
Click to collapse
Thanks a lot I will take a look tomorrow and see what I can do
Sent from my GT-I9505G using Tapatalk 2

illogic6 said:
Here's the ROM I was messing with. I used the "old firmware" because it was the newest one when I first looked. http://forum.xda-developers.com/showthread.php?t=2349369
I've attached my modded updater script. (You will have to remove the .txt extension. Wouldn't let me upload without it.) All I had to do was edit which /dev/block the script mounts before it copies stuff over. If I recall correctly, I only had to change the dev it flashes the boot.img to. See this post: http://forum.xda-developers.com/showpost.php?p=43843048&postcount=30
include 'standard_disclaimer.php';
Click to expand...
Click to collapse
Great work Illogic I wonder why TW will not display I tried as well but I did not get as far as you mine fails during the installation.
Also did you see my post on getting Cygwin to set device mount points that in itself will speed things up
Sent from my GT-I9505G using Tapatalk 2

MJHawaii said:
Great work Illogic I wonder why TW will not display I tried as well but I did not get as far as you mine fails during the installation.
Also did you see my post on getting Cygwin to set device mount points that in itself will speed things up
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
I haven't used Cygwin before. I'll take a look at it today.
Also going to mess around with TW a little more. Maybe we just need some libs from the stock 9505g rom or something.
Update: I'm afraid I may have mislead you earlier. It appears that you need more than just the updated update-script in order to get touchwiz to boot. You also need a kernel from one of the 4.3 leaks. Here's the one I've been using. (Attached) Not only does it boot, but the soft keys work and you can hear the sound effects of the lock screen. I'm very close.

illogic6 said:
I haven't used Cygwin before. I'll take a look at it today.
Also going to mess around with TW a little more. Maybe we just need some libs from the stock 9505g rom or something.
Update: I'm afraid I may have mislead you earlier. It appears that you need more than just the updated update-script in order to get touchwiz to boot. You also need a kernel from one of the 4.3 leaks. Here's the one I've been using. (Attached) Not only does it boot, but the soft keys work and you can hear the sound effects of the lock screen. I'm very close.
Click to expand...
Click to collapse
Wow Illogic your close bro thanks for your hard work the libs does sound like it would cause the display problem I'm gonna play around with this too. All I did was unpack stock 4.3 and zip and deo the files with root. The problem I am having is that I am still learning U-scripts and so I cannot get anything to flash. I get failed on 0p21 even though its changed. Maybe I can pm you what I did later and get your feedback cuz your miles ahead of me
Sent from my GT-I9505G using Tapatalk 2

I've merged libs from the leaked 4.3 build into the TW ROM without overwriting anything. Didn't seem to change anything. At this point, I'm playing with magic I don't understand so not sure how much farther I'm going to get.
Would really like figure out which files in the system are responsible for the display. Perhaps we need to overwrite those files. Google is failing me so far.
---------- Post added at 04:45 PM ---------- Previous post was at 04:29 PM ----------
Tada! :victory:
The error message goes away. Right now, the web browser force closes... that might be because of the ROM I was modifying. What I did was use the 4.2.2 kernel that shipped with the google play phones. That booted AND activated the display.
http://i.imgur.com/HZaraPK.jpg

[TUT] Implementing EPRJ RIL in Custom Roms by Yourself

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)

[ROM][Unofficial]SlimBean - The Menu Returns [build.2.1] [5-Nov-13]

Here's presenting stock Slimbean ROM with just 2 commits reverted which prevented users from adding the big menu button to navigation bar and SlimPie. Besides this, this is pure Slimbean without any modification whatsoever. I'm not a developer, in fact I learnt to install linux because I wanted the menu button so bad. I thought maybe I should share this with similar minded people. I'm going to upload updates as and when Slim team releases 4.3 updates as I'm not sure about the changes that would be made in 4.4. I won't be able to take any request as I am totally unaware of how to make any modifications, cherry picks or anything else. Hope you enjoy this ROM.
Code:
Disclaimer: We are not responsible for any damages on your device.
Original Slim Features:
The Real Dark Slim
SlimPIE
Notification drawer Shortcuts
Full hardware key rebinding!
Keyboard rotation
SlimCenter, SlimIRC and much more
Full feature list and changelog can be found on Slimroms website.
Installation instructions
For most users
Please keep in mind if a special instruction is needed it will be noted in the changelog.
Download the latest build from
Addons
!Recommended! Full wipe, and manual format /system
Flash ROM and the addons you want, reboot
Source
This ROM and kernel uses stock Slimbean code, which again can be accessed through Slimroms website.
Credits:
mar5hal
Nebucatnetzer [Slimroms forum]
NeB [Slimroms forum]
kufikugel
Entire Slimroms team for the source code.
Slim team has done an excellent job, please consider donating them.
Download Link:
http://d-h.st/DDf
[If you want to make a mirror, please contact me to update the OP]

Reserved...

another one... just in case...

@gururoop thank you so much for this, the one main thing missing from slim, Menu Button. In theory there shouldn't be any issues since its only 2 extra commits. Downloading now :good:

Just some screens to confirm. Everything is running smooth, no issues whatsoever
Sent from my Nexus 4 using XDA Premium 4 mobile app

Great, thanks a lot
edit: glad to have the menu button back.
However, I think it's better if you just make a small patch instead of rebuild the whole rom.

dark_ente said:
However, I think it's better if you just make a small patch instead of rebuild the whole rom.
Click to expand...
Click to collapse
That would be great, indeed. :good:

dark_ente said:
Great, thanks a lot
edit: glad to have the menu button back.
However, I think it's better if you just make a small patch instead of rebuild the whole rom.
Click to expand...
Click to collapse
finistere said:
That would be great, indeed. :good:
Click to expand...
Click to collapse
i wish i knew how to do that, but if you guys know how to, please guide me and i'll do it...
anyway, just compiled a new build so uploaded it here... OP updated with new link... enjoy...

gururoop said:
i wish i knew how to do that, but if you guys know how to, please guide me and i'll do it...
anyway, just compiled a new build so uploaded it here... OP updated with new link... enjoy...
Click to expand...
Click to collapse
Changelog what is changed?

The new official one has the statusbar mods now. Hate to leave it for the menu key but I might. Thanks for the build.
Sent from my Nexus 4 using Tapatalk

smartymcfly said:
Changelog what is changed?
Click to expand...
Click to collapse
No changelog... Just wanted to check how long does it take to compile in a virtualbox so synced the latest code and compiled...
Sent from my Nexus 4 using xda premium

scottx . said:
The new official one has the statusbar mods now. Hate to leave it for the menu key but I might. Thanks for the build.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
What statusbar mods are you talking about? This build is pure stock with just 2 reverts which enable us to add the menu button, apart from that no other change. The latest build was synced on 5th November, so maybe the statusbar mods were added later.
Sent from my Nexus 4 using xda premium

gururoop said:
i wish i knew how to do that, but if you guys know how to, please guide me and i'll do it...
anyway, just compiled a new build so uploaded it here... OP updated with new link... enjoy...
Click to expand...
Click to collapse
Please correct me if I'm wrong.
I guess you revert the change in framework-res.
In that case, you just need to create an update.zip which replace the old framework-res with your framework-res, and user only need to flash that file instead of the whole ROM.

dark_ente said:
Please correct me if I'm wrong.
I guess you revert the change in framework-res.
In that case, you just need to create an update.zip which replace the old framework-res with your framework-res, and user only need to flash that file instead of the whole ROM.
Click to expand...
Click to collapse
i revert the following 2 commits to achive the desired change:
5dd205257a8cfba3278ddb4ffbdd1897b1feaed7-packages/apps/Settings
8108afc56d15553c1d4abc83c9e9e27ac5b7cb36-framework/base
don't know exactly how many files or what else changes due to that. If you could figure that out, i'll be more than happy to help. and can u tell me whether there is any way i can compile some selected files instead of the whole rom?

gururoop said:
i revert the following 2 commits to achive the desired change:
5dd205257a8cfba3278ddb4ffbdd1897b1feaed7-packages/apps/Settings
8108afc56d15553c1d4abc83c9e9e27ac5b7cb36-framework/base
don't know exactly how many files or what else changes due to that. If you could figure that out, i'll be more than happy to help. and can u tell me whether there is any way i can compile some selected files instead of the whole rom?
Click to expand...
Click to collapse
What I mean is you still compile the rom, but only make a flashable zip of these two files and put it here. It would be easier for both you and me.
From the commit, I guess the two files are settings.apk and framework-res
Sent from my Nexus 4 using Tapatalk 2

dark_ente said:
What I mean is you still compile the rom, but only make a flashable zip of these two files and put it here. It would be easier for both you and me.
From the commit, I guess the two files are settings.apk and framework-res
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
now its getting too embarassing for me, but do you have any easy guide to help me create a flashable zip for these two files??

gururoop said:
now its getting too embarassing for me, but do you have any easy guide to help me create a flashable zip for these two files??
Click to expand...
Click to collapse
No problem mate.
The easiest way is to extract your rom to a new folder, delete boot.img, go to system folder and delete everything except the two files you want to keep. (you must also keep the folder structure). Inside these 2 folders are only files you want to copy (in this case settings.apk and framework-res)
Then go to META-INF\com\google\android\ folder and use notepad to edit the updater-script file like this
After that, you can compress them as simple zip and flash via twrp.
Next time you can just replace 2 files, compress again. No need to edit updater-script
Sent from my Nexus 4 using Tapatalk 2

dark_ente said:
No problem mate.
The easiest way is to extract your rom to a new folder, delete boot.img, go to system folder and delete everything except the two files you want to keep. (you must also keep the folder structure). Inside these 2 folders are only files you want to copy (in this case settings.apk and framework-res)
Then go to META-INF\com\google\android\ folder and use notepad to edit the updater-script file like this
After that, you can compress them as simple zip and flash via twrp.
Next time you can just replace 2 files, compress again. No need to edit updater-script
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
So what you are saying is that if someone or I can just extract those 2 apks and add to a flashable zip I have lying round and menu button will be added to normal slim?

Would have been quicker!!
Sent by mobile telephone.

^^^^LOL I agree... Sidenote its funny how many people can creates so much goodness with building or modding files but dont know how to create flashable zips... LOL
dont re-invent the wheel I believe just get a gapps zip and mod away...
OH yea my bad thanks for the rom I too am a big fan of the menu and choose to live with it