Related
Hi.
If someone have improvement advices for this thread PM me.
This won't work for sense ir smth similar.
I'm not responsible for bricked(or smth similar) devices cause of ROMS ported by this method.
I don't know if this works for non-aosp/cm based ROMS. You may need to do some more things to get it working.
Try to use the same android version for both ROMS For 4.2.2 use Cm For 4.1.2 use Stock ROM.
You won't have a compatible source code. This means you can't update the ROM through syncing and recompiling. But you won't need a Linux distro fot this Method.
Actually its very easy.
firstly follow this tutorial: http://www.fesilo.com/forum/android/guides/113-guide-guide-to-port-roms-fast-and-easy to get a booting ROM
then download this Tool -> http://www.virtuous-ten-studio.com/ it makes de/re-compiling very easy.
now you just have to fix those anoying bugs
to fix Phone.apk FC.
Be sure to put in the submenu smali API level to Android 4.2.2(in VTS) and tick use smali debug output and in the submenu build tick use old signature
Decompile telephony-common.jar from both ROMS.
Copy the X3RIL.smali found in /com/android/internal/telephony from the .jar of your base ROM (cm 10.1,stock rom) to the .jar of the ROM you're trying to port.
Recompile and replace the one within your old one from HOX ROM.
Decompile framework-res.apk from both ROMS.
open /res/values/arrays.xml
press Control+f to use the search function.
enter auto
copy the arrays config_autoBrightnessLevels,config_autoBrightnessLcdBacklightValues,config_autoBrightnessButtonBacklightValues,config_autoBrightnessKeyboardBacklightValues to the .xml off your ROM and overwrite the old ones.
then copy and overwrite power_profile.xml and storage_list from your base ROM to the ROM your trying to port.
Recompile and replace the one within your old one from HOX ROM.
actually this was the magic.
I hope I forgot nothing. Please Excuse me If I did. It's half past 23 here and I had a very exhausting Weekend.
I will update this thread in a few days to make it more userfriendly
You can PM me if you have Questions.
BIG THANKS TO SNXO FOR GIVING ME THE KNOW-HOW TO FIX BIG ISSUES.
and sorry for my English
reagards tobixdev
Thanks..
Very Interesting and useful..
Infact i find some guide simple to try...
Good Job!
Very nice Tobi good job :thumbsup:
Hopefully that gives power to the people for making some good Roms and Programms for us. It isn't that difficult to do just a little bit reading and then learning by doing.
Best regards SnXo
Notice that will work with every rom. The easy way is snap from HOX but you can choose Roms from others too... To keep it iesy you should have the same resolution and Androidversion nothing more... That's it!
Maybe a admin can make this as sticky that would be nice
Sent from my LG-P880 using XDA Premium HD app
SnXo said:
Very nice Tobi good job :thumbsup:
Hopefully that gives power to the people for making some good Roms and Programms for us. It isn't that difficult to do just a little bit reading and then learning by doing.
Best regards SnXo
Notice that will work with every rom. The easy way is snap from HOX but you can choose Roms from others too... To keep it iesy you should have the same resolution and Androidversion nothing more... That's it!
Maybe a admin can make this as sticky that would be nice
Sent from my LG-P880 using XDA Premium HD app
Click to expand...
Click to collapse
thanks
anyone tried yet ?
Sent from my LG-P880 using xda app-developers app
tobixdev said:
thanks
anyone tried yet ?
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
I tried a while ago with this rom: http://forum.xda-developers.com/showthread.php?t=1562603.
The end result was a bootloop. I will maybe try to do it again when I have more time.
this doesn't work with sense without additional work.
Sent from my LG-P880 using xda app-developers app
tobixdev said:
Hi.
If someone have improvement advices for this thread PM me.
This won't work for sense ir smth similar.
I'm not responsible for bricked(or smth similar) devices cause of ROMS ported by this method.
I don't know if this works for non-aosp/cm based ROMS. You may need to do some more things to get it working.
Try to use the same android version for both ROMS For 4.2.2 use Cm For 4.1.2 use Stock ROM.
You won't have a compatible source code. This means you can't update the ROM through syncing and recompiling. But you won't need a Linux distro fot this Method.
Actually its very easy.
firstly follow this tutorial: http://www.fesilo.com/forum/android/guides/113-guide-guide-to-port-roms-fast-and-easy to get a booting ROM
then download this Tool -> http://www.virtuous-ten-studio.com/ it makes de/re-compiling very easy.
now you just have to fix those anoying bugs
to fix Phone.apk FC.
Be sure to put in the submenu smali API level to Android 4.2.2(in VTS) and tick use smali debug output and in the submenu build tick use old signature
Decompile telephony-common.jar from both ROMS.
Copy the X3RIL.smali found in /com/android/internal/telephony from the .jar of your base ROM (cm 10.1,stock rom) to the .jar of the ROM you're trying to port.
Recompile and replace the one within your old one from HOX ROM.
Decompile framework-res.apk from both ROMS.
open /res/values/arrays.xml
press Control+f to use the search function.
enter auto
copy the arrays config_autoBrightnessLevels,config_autoBrightnessLcdBacklightValues,config_autoBrightnessButtonBacklightValues,config_autoBrightnessKeyboardBacklightValues to the .xml off your ROM and overwrite the old ones.
then copy and overwrite power_profile.xml and storage_list from your base ROM to the ROM your trying to port.
Recompile and replace the one within your old one from HOX ROM.
actually this was the magic.
I hope I forgot nothing. Please Excuse me If I did. It's half past 23 here and I had a very exhausting Weekend.
I will update this thread in a few days to make it more userfriendly
You can PM me if you have Questions.
BIG THANKS TO SNXO FOR GIVING ME THE KNOW-HOW TO FIX BIG ISSUES.
and sorry for my English
reagards tobixdev
Click to expand...
Click to collapse
ths very much
Hi all !
So, for you all, the user of SlimKat for L7 might encounter these signal bar bugs.
The bug is mostly (and most) noticeable bug in this ROM.
By following this guide, you agree to my conditions :
a. I won't respond to 'how to do it ?' and 'can you do it ?' or 'will you do it for me ?' question.
b. I also won't respond to 'how can I decompile .jars ?' and 'what is this ?' question, these questions can easily answered by searching Google.
c. No, I won't make a flashable zips for you, you've to do this alone. Because I want you to understand, 'what does happen if I do this ?'. So I want you to do this all by yourself.
d. Only use question for last resort (means, even by searching Google, you don't find answer to your problem)
After you read those conditions, here's the guide.
1. Decompile SlimKat framework.jar
2. Decompile other ROM (with working signal bar) framework.jar
3. Open smali/android/telephony/
4. Copy all file named CellSignalStrength and SignalStrenght from other ROM framework.jar. See CALIBAN's post for needed file to copy + screenshot.
5. Copy all of those file to SlimKat framework.jar (in the same directory, smali/android/telephony)
6. Compile SlimKat framework.jar
7. Copy modified classes.dex to original unmodified SlimKat framework.jar
8. Push the modified framework.jar to /system/framework (or add it to SlimKat zipfile)
9. Reboot (if you push it) or reflash SlimKAT, then wipe dalvik cache & cache (if you add it to SlimKat zipfile)
Thanks to -CALIBAN666- for fixing the guide !
Credits for this guide :
- SlimROMs Team : Providing a great ROM for us to use
- CM Team : No need to explain, they're a great developers. Without them, there won't be a proper working KitKat for our device.
- Optima Team : By always supporting me in every conditions
- -CALIBAN666- : Trying this tutorial, and becoming my best friend in XDA
- Google : My teacher
- Stackoverflow Members : Providing workaround for every eror
- brut.all & iBotPeaches : APKTool, the greatest tool to reverse-engineering in Android
bro its for l5 too,by the way,to make it work i must the 2 signalstrenght smalis at the bottom from telephony changing too,otherwise i have become issues with dialer and mms app.
i have attached two pics with needed smalis,created with windows screenshot.
-CALIBAN666- said:
bro its for l5 too,by the way,to make it work i must the 2 signalstrenght smalis at the bottom from telephony changing too,otherwise i have become issues with dialer and mms app.
i have attached two pics with needed smalis,created with windows screenshot.
Click to expand...
Click to collapse
Thanks bro !
Will post this to first post.
hey bro,i dont know you remember,because today i was looking in old android files on my pc and i found one of the first tweak i used which has realy worked for me,it was activo speeder,so we know us minimum 1/5 years on xda,lol.another question is,you are from the flowercity called bandung,so you know xda member evanlocked?he came from same city.
-CALIBAN666- said:
hey bro,i dont know you remember,because today i was looking in old android files on my pc and i found one of the first tweak i used which has realy worked for me,it was activo speeder,so we know us minimum 1/5 years on xda,lol.another question is,you are from the flowercity called bandung,so you know xda member evanlocked?he came from same city.
Click to expand...
Click to collapse
Activo Speeder... Yep, that was my first tweak ever made for XDA
evanlocked... I think I've seen him somewhere in XDA.
Sent from my Z4D-25232 using XDA Premium 4 mobile app
Thanks man for the guide. I used this guide on my LG Optimus G Pro.
However for me, copying the classes.dex file to the framework.jar did not make any changes. But flashing the modified framework.jar in the build>apk folder did the trick.
Thanks a million.
arifqur said:
Thanks man for the guide. I used this guide on my LG Optimus G Pro.
However for me, copying the classes.dex file to the framework.jar did not make any changes. But flashing the modified framework.jar in the build>apk folder did the trick.
Thanks a million.
Click to expand...
Click to collapse
Glad it worked well on your device, thanks for trying my guide too
Well this Guide with all its spelling mistakes somehow made it to portal
Click to expand...
Click to collapse
For Developers: If you are planning to compile your ROM, and want to use this mod, then read This Post
Background Story:
I was missing the CyberShot Camera too much and found Google Camera has been ported to JB And I also wanted to try the Moded LifeLog app, which somehow was not working on my Pacman Rom.
These were the reasons I Decided to come back to JB Stock Base. I had a previous Nandroid Backup of Lovin's Z2 ROM for XV. I took all my Call-Log and SMS Backups and also took backup of some apps that I used. Then I restored the NAND Backup today.
after that I started restoring the apps+data. Everything was fine.
After few hours of using, As I always do, I took the periodic backup of my Call Logs again. That's when I noticed, the previous Logs were 700+ and now after making some calls, it came down to 500. after Some test, I found out, this is not problem of Backup software.
A little Google search revealed Android has a default call log limit set to 500 Calls.
I searched for Xposed Mod for this, found TrimNot. But it showed error. Most probably, it is only for KK. Then I thought why not MOD it myself?
That's how it all started...
The research & work procedure:
I first thought, OK, I need to find where the Calls are stored. After passing some time with Google, I found, the Logs are stored in a SQlite3 Database, in
Code:
/data/data/com.android.providers.contacts/databases/contacts2.db
There is no limit in this database storage. So, the limit must be in the code.
After another couple of hours, I found that Android checks if the contacts has reached 500 then removes the older. Searching with
Call Log Android
Click to expand...
Click to collapse
in android API reference, where I found some leads on my research.
"public class CallLog" which is under "android.provider.CallLog"
Something told me, to look for this class, in the actual source code. But that's almost 30 GB and I don't have time. from some prior Java knowledge I knew, all class have their own source file, with the same name, So the name would be "CallLog.java"
Now I searched Google, with it and found exactly what I was looking for. The search took me to a Git page android/platform_frameworks_base
And here I found this code.
Java:
private static void removeExpiredEntries(Context context) {
final ContentResolver resolver = context.getContentResolver();
resolver.delete(CONTENT_URI, "_id IN " +
"(SELECT _id FROM calls ORDER BY " + DEFAULT_SORT_ORDER
+ " LIMIT -1 OFFSET 500)", null);
}
The file is located in
Code:
platform_frameworks_base/core/java/android/provider/CallLog.java
and from the name I guessed, this should be inside framework files. Then I went into action. I first tried to de-compile the framework-res.apk file. I used Advanced APKTool by BDFreak
Using the windows search tool, I searched for "call log". I found nothing. Then I tried to de-compile "framework.jar". For this, I followed guide by Rizal Lovins - [Share Latest Apktool 4.2.2/Guide/Tutorial/] How to Decompile/Compile/Sign Apk/Jar
after the de-compiling was Done, I found there is a "android/provider" folder. Yes, it look similar to "platform_frameworks_base/core/java/android/provider/CallLog.java"
So, here should be the files. And I found Two files
Code:
CallLog$Calls.smali
CallLog.smali
I opened both with Notepad++,
CallLog.smali gave me noting.
But after a careful search, I found the exact query inside the ]CallLog$Calls.smali file.
I found this line -
Code:
const-string v2, "_id IN (SELECT _id FROM calls ORDER BY date DESC LIMIT -1 OFFSET 500)"
I just changed 500 to 100000 and I knew my task was done.
I then recompiled the framework.jar and took backup of my original framework.jar (took Nandroid backup ), replaced the original with my modified JAR file. Set the permission rw-r-r or 644. Then rebooted my phone.
Testing:
After the phone started, I made a call, then took backup of the Call Log with Call Log Backup Restore it showed 501.
This means my task is done.
Then I thought, why not share the whole experience today in XDA. So I started Writing this Guide.
F.A.Q.
Why I need more than 500 Call Log ?
- Well I work in Billing Department of a GSM Phone Exchange/Gateway. I periodically cross check my phone Call Logs with the Exchange SoftSwitch Data. Except for that, It's just fun to try something new.
Why this guide has no steps or required steps?
- Because, if anything I missed, those will be added later in the FAQ, from the comments.
Is this tested on any device?
-Yes,
My # Xperia V with LOVINS X™ Z2 ROM 9.2.A.2.5
# Xperia V NeoWave™ ROM
# Xperia TX OmniRom
# Xperia TX (unknown ROM )
# Xperia Z2 (unknown ROM )
# Xperia P Stock ROM
#Xperia P JB based Enigma v7.2 ROM
#CyanogenMod 11 M11 and M12
Can this work on my T/TX/TL/Z/Z1 etc. etc.
- Theoretically it should work on any Device and any ROM. But, practically, I don't know, why don't you try yourself and let me know
I'm newbie, can you provide me more simple guide?
- Well I'm a Newbie myself Just take a Nandroid Backup and start the process. What can go wrong? At most you'll have to restore the backup.
Go to every link and read those too. And Don't forget to Thank those people who provided the Tools and Guides.
Still If you don't understand my guide, read it twice, if it doesn't work read again.
Ha Ha Ha kidding. Here you go A Simple guide
Update:
If you are planning to compile your ROM, and want to use this mod, then read This Post
I switched to NeoWave™ ROM and just as usual applied my MOD. Restored 800+ Call Log from Backup. Now I find another limitation. It's in the Dialer. In the KitKat Call History, there is a Statistics option. Here it always shows
TOTAL: 500 Calls,....
Click to expand...
Click to collapse
So Now I'm digging the sources again to make the stats go higher.
Update: The issue was caused because, after sometimes (any call), the call history automatically turned to 500. Because the framework.jar was odexed and i guess, odex file had the old value set again. And for the NeoWave I used android MultiTool, it showed one error while compiling, Unsigned Short value exceeds, I didn't notice that. My bad. Now I have done the Mod again with Apktool (Lovins shared one) and removed the odex file and then Everything seems fine. Even the Statistics Shows, TOATAL: 1203 Calls, ....
Tested on OmniRom and works as expected. I've used an Xposed module before which does the same thing, but it's always nice to find new ways to implement things without having to use Xposed.
Antiga Prime said:
Tested on OmniRom and works as expected. I've used an Xposed module before which does the same thing, but it's always nice to find new ways to implement things without having to use Xposed.
Click to expand...
Click to collapse
Thanks for the Confirmation. I am updating the Tested Device & ROM. Your device is TX, Right? I guessed from the signeture
Antiga Prime said:
Tested on OmniRom and works as expected. I've used an Xposed module before which does the same thing, but it's always nice to find new ways to implement things without having to use Xposed.
Click to expand...
Click to collapse
Would you like to share the Xposed module you used before?
pollob666 said:
Thanks for the Confirmation. I am updating the Tasted Device & ROM. Your device is TX, Right? I guessed from the signeture
Click to expand...
Click to collapse
Yes, I have a TX.
tianzhisun said:
Would you like to share the Xposed module you used before?
Click to expand...
Click to collapse
It's the same one linked in the OP, except it's named TrimNot, not TimNot. I thought it might be a different one given that the one linked above didn't work for @pollob666, but I guess it's because I'm on a 4.4 ROM.
It's the same one linked in the OP, except it's named TrimNot, not TimNot. I thought it might be a different one given that the one linked above didn't work for @pollob666, but I guess it's because I'm on a 4.4 ROM.
Click to expand...
Click to collapse
Oops.. It was a Typo Yes, TrimNot works on KK but not on JB. that is why I needed to modify my Android Framework.
This is great and I will try it out.
But there is also another ridiculous limitation, that is the maximum of 20 alarms you can have in the clock
acb123 said:
This is great and I will try it out.
But there is also another ridiculous limitation, that is the maximum of 20 alarms you can have in the clock
Click to expand...
Click to collapse
for the clock there is this guide http://forum.xda-developers.com/showpost.php?p=53591001&postcount=6 give it a look
acb123 said:
This is great and I will try it out.
Click to expand...
Click to collapse
After trying, give us the update.
But there is also another ridiculous limitation, that is the maximum of 20 alarms you can have in the clock
Click to expand...
Click to collapse
I didn't notice that. Let's see what we can do about that
pollob666 said:
I didn't notice that. Let's see what we can do about that
Click to expand...
Click to collapse
give a look at the link in the post above yours... it's for z2 but it could work also for other version
Works fine on Xperia P running JB based Enigma v7.2
It works on stock based Xperia P. pollob666 small typo. How about renaming "tasted" to "tested"
usb2 said:
give a look at the link in the post above yours... it's for z2 but it could work also for other version
Click to expand...
Click to collapse
Yeah, saw that, going to try it tomorrow. Hopefully, here I can find some DB sources too.
prasadkumar013 said:
It works on stock based Xperia P. pollob666 small typo. How about renaming "tasted" to "tested"
Click to expand...
Click to collapse
Sorry about that, I guess I'll have to check the whole OP
Please make the steps simple for a newbie
Well, I was looking for this feature since Google invented Android!:good:
I was using MIUI because of they're giving unlimited Call log. Then some one invented TrimNot on Aug 15, 201, I came again to OzcanRom (My Fav). Trim not doesn't work at all.
My question is, Can you make this step more simple. I'm a new bie. :fingers-crossed:
pollob666 said:
Background Story:
I was missing the CyberShot Camera too much and found Google Camera has been ported to JB And I also wanted to try the Moded LifeLog app, which somehow was not working on my Pacman Rom.
These were the reasons I Decided to come back to JB Stock Base. I had a previous Nandroid Backup of Lovin's Z2 ROM for XV. I took all my Call-Log and SMS Backups and also took backup of some apps that I used. Then I restored the NAND Backup today.
after that I started restoring the apps+data. Everything was fine.
After few hours of using, As I always do, I took the periodic backup of my Call Logs again. That's when I noticed, the previous Logs were 700+ and now after making some calls, it came down to 500. after Some test, I found out, this is not problem of Backup software.
A little Google search revealed Android has a default call log limit set to 500 Calls.
I searched for Xposed Mod for this, found TrimNot. But it showed error. Most probably, it is only for KK. Then I thought why not MOD it myself?
That's how it all started...
The research :
I first thought, OK, I need to find where the Calls are stored. After passing some time with Google, I found, the Logs are stored in a SQlite3 Database, in
Code:
/data/data/com.android.providers.contacts/databases/contacts2.db
There is no limit in this database storage. So, the limit must be in the code.
After another couple of hours, I found that Android checks if the contacts has reached 500 then removes the older. Searching with
in android API reference, where I found some leads on my research.
"public class CallLog" which is under "android.provider.CallLog"
Something told me, to look for this class, in the actual source code. But that's almost 30 GB and I don't have time. from some prior Java knowledge I knew, all class have their own source file, with the same name, So the name would be "CallLog.java"
Now I searched Google, with it and found exactly what I was looking for. The search took me to a Git page android/platform_frameworks_base
And here I found this code.
Java:
private static void removeExpiredEntries(Context context) {
final ContentResolver resolver = context.getContentResolver();
resolver.delete(CONTENT_URI, "_id IN " +
"(SELECT _id FROM calls ORDER BY " + DEFAULT_SORT_ORDER
+ " LIMIT -1 OFFSET 500)", null);
}
The file is located in
Code:
platform_frameworks_base/core/java/android/provider/CallLog.java
and from the name I guessed, this should be inside framework files. Then I went into action. I first tried to de-compile the framework-res.apk file. I used Advanced APKTool by BDFreak
Using the windows search tool, I searched for "call log". I found nothing. Then I tried to de-compile "framework.jar". For this, I followed guide by Rizal Lovins - [Share Latest Apktool 4.2.2/Guide/Tutorial/] How to Decompile/Compile/Sign Apk/Jar
after the de-compiling was Done, I found there is a "android/provider" folder. Yes, it look similar to "platform_frameworks_base/core/java/android/provider/CallLog.java"
So, here should be the files. And I found Two files
Code:
CallLog$Calls.smali
CallLog.smali
I opened both with Notepad++,
CallLog.smali gave me noting.
But after a careful search, I found the exact query inside the ]CallLog$Calls.smali file.
I found this line -
Code:
const-string v2, "_id IN (SELECT _id FROM calls ORDER BY date DESC LIMIT -1 OFFSET 500)"
I just changed 500 to 100000 and I knew my task was done.
I then recompiled the framework.jar and took backup of my original framework.jar (took Nandroid backup ), replaced the original with my modified JAR file. Set the permission rw-r-r or 644. Then rebooted my phone.
Testing:
After the phone started, I made a call, then took backup of the Call Log with Call Log Backup Restore it showed 501.
This means my task is done.
Then I thought, why not share the whole experience today in XDA. So I started Writing this Guide.
F.A.Q.
Why I need more than 500 Call Log ?
- Well I work in Billing Department of a GSM Phone Exchange/Gateway. I periodically cross check my phone Call Logs with the Exchange SoftSwitch Data. Except for that, It's just fun to try something new.
Why this guide has no steps or required steps?
- Because, if anything I missed, those will be added later in the FAQ, from the comments.
Is this tested on any device?
-Yes,
My # Xperia V with LOVINS X™ Z2 ROM 9.2.A.2.5
# Xperia TX OmniRom
# Xperia TX (unknown ROM )
# Xperia Z2 (unknown ROM )
# Xperia P Stock ROM
Can this work on my T/TX/TL/Z/Z1 etc. etc.
- Theoretically it should work on any Device and any ROM. But, practically, I don't know, why don't you try yourself and let me know
Click to expand...
Click to collapse
---------- Post added at 11:08 AM ---------- Previous post was at 10:10 AM ----------
Can you please share the framework.jar file that edited and recompiled by you? If you can make a edited framework.jar for OzcanRom 4.2, I will be very thankful. I spent almost two nights on this and failed. Please help. :silly::fingers-crossed:
Antiga Prime said:
Tested on OmniRom and works as expected. I've used an Xposed module before which does the same thing, but
it's always nice to find new ways to implement things without having to use Xposed.
Click to expand...
Click to collapse
A Simpler guide
jamoen said:
My question is, Can you make this step more simple. I'm a new bie. :fingers-crossed:
Can you please share the framework.jar file that edited and recompiled by you? If you can make a edited framework.jar for OzcanRom 4.2, I will be very thankful. I spent almost two nights on this and failed. Please help. :silly::fingers-crossed:
Click to expand...
Click to collapse
No need to Quote the whole OP
My framework.jar won't work for you. We need to modify your ROM's framework.jar if you can provide me that file, I can MOD it for you.
But, I am giving the Simple steps. I would be very happy if you can do it yourself.
I am assuming you already have Notepad++ or Similar text editing tool and know how to pull files from /system
Step 1: Download APKTool of your choice. I used Advanced APKTool by BDFreak
Step 2: Decompile your framework.jar. For this, I followed guide by Rizal Lovins - [Share Latest Apktool 4.2.2/Guide/Tutorial/] How to Decompile/Compile/Sign Apk/Jar
Step 3: Open the CallLog.smali file and any other files that starts with CallLog ( like in my case CallLog$Calls.smali ) in Notepad++ or any other Text Editor.
Step 4: search for "SELECT _id FROM calls ORDER BY" or similar lines. You will find LIMIT -1 OFFSET 500 change 500 with any number you want.
Step 5: Save the modified file smali, and recompile the jar file.
Step 6: Just to be safe, take a NANDROID backup.
Step 7: Take a backup of the original framework.jar, delete it from system and push the modified framework.jar to System and change permission to rw-r-r or 644. Reboot.
Step 8: test
I couldn't find Provider folder. Please help.
I couldn't find Provider folder. Please help.
Failed! Please help
pollob666 said:
No need to Quote the whole OP
Click to expand...
Click to collapse
Thank you for the reply.
I could not find any folder called Provider. Searched all folders and failed to find a call entry.
I took the framework.jar from system folder. Any wrong?
Attached my framework.jar file. Please help me.
Found the string in framework2.jar and edited. Success!!
Please help me to push it again...
Can I use esfile explorer?
---------- Post added at 02:31 PM ---------- Previous post was at 02:09 PM ----------
jamoen said:
Found the string in framework2.jar and edited. Success!!
Please help me to push it again...
Can I use esfile explorer?
Click to expand...
Click to collapse
Unfortunately.. The method failed. Going back to MIUI in tears..
jamoen said:
Found the string in framework2.jar and edited. Success!!
Please help me to push it again...
Can I use esfile explorer?
---------- Post added at 02:31 PM ---------- Previous post was at 02:09 PM ----------
Unfortunately.. The method failed. Going back to MIUI in tears..
Click to expand...
Click to collapse
WOW, you really did it. Sorry I was in training my juniors at office, didn't reply earlier.
You can use es explorer, or if you have adb, then you can use some shell commands. I can give you the commands, if you haven't done it already.
It should work. Let me check and mod a it for you.
Edit: Sorry, I don't have the framework2.jar. ant the ROM is too big for downloading now at office. But for Samsung device, I guess the re-compile process needs a bit working. you need to recompile the file, then open it in 7zip or WinRAR replace the AndroidManifest file with the file of the original, (then sign it then zipalign it not sure for jar file though). Then push it to the system.
pollob666 said:
WOW, you really did it. Sorry I was in training my juniors at office, didn't reply earlier.
You can use es explorer, or if you have adb, then you can use some shell commands. I can give you the commands, if you haven't done it already.
It should work. Let me check and mod a it for you.
Edit: Sorry, I don't have the framework2.jar. ant the ROM is too big for downloading now at office. But for Samsung device, I guess the re-compile process needs a bit working. you need to recompile the file, then open it in 7zip or WinRAR replace the AndroidManifest file with the file of the original, (then sign it then zipalign it not sure for jar file though). Then push it to the system.
Click to expand...
Click to collapse
I double checked it. Again extracted the framework.jar and decompliled it.The string of 100000 is there. But this thing is not working. I don't know why.
Can I share you the framework2.jar with you?
jamoen said:
I double checked it. Again extracted the framework.jar and decompliled it.The string of 100000 is there. But this thing is not working. I don't know why.
Can I share you the framework2.jar with you?
Click to expand...
Click to collapse
I will modify it and upload it for you. But I guess I will need the framework-res.apk with it. if there is any. But, I'm going home now, I'll update you by 11pm.
*EDIT* This thread is now based upon the work by @fattire and @slayher, who got it up on the 910T. For that phone see this thread: http://forum.xda-developers.com/not...nt/unoffcial-cm-12-0-t-mobile-note-4-t2964887
This thread is for dev's interested to help out porting CM12 to our device. I've researched for info regarding CM ports and good information is actually quit scarce. A dev might post something like 'hmm stuck at boot anim' and then the next day 'got it, booting now !' without explaining what he did to solve it. I want to change that, so this thread can serve as a guide for other first time porters too (this is also my first porting project), documenting every step as in much detail as possible.
For ROMS: http://forum.xda-developers.com/not...official-cm-12-0-910f-note-4-trltexx-t2987412
Please use this thread for R&D/development ONLY !!!
Ok, I'm really starting from scratch and never done any phone ROM porting. I've just made a new virtual disk running ubuntu and am currently downloading the CM12 repo. I figured, how to get even started here. I figured that the goals we need to attain in this order:
1) compile the kernel samsung supplied
2) make sure we can boot into kernel
3) get ADB up and running
4) get CM12 starting up, even the bootanim alone would be a nice goal to reach
5) Booting into homescreen
6) Fixing all stuff like modem, wifi etc etc etc
Anyway, I'm currently downloading CM12 sources as we speak ...
This is by the way a link I found very useful: http://www.androidenea.com/2009/08/init-process-and-initrc.html It describes the Android init process, cause I was wondering, how to even start all this ? How to get from kernel to CM booting: that's where init.rc should come into play of course
Good luck this is a long project. I build carbonrom for another phone where everything for cm was allready fixed. I would start with a phone that allready has support to learn how the process goes. You can brick your phone and it's a process of trail and error... But I hope you manage good luck!
KaptKeefmenneke said:
Good luck this is a long project. I build carbonrom for another phone where everything for cm was allready fixed. I would start with a phone that allready has support to learn how the process goes. You can brick your phone and it's a process of trail and error... But I hope you manage good luck!
Click to expand...
Click to collapse
I'm not sure I understand what you mean ? If the phone already has support, then what's there to port ? Or do you mean building CM itself ? That I've done quite a few times already, did quite a bit of work on the i9500, fixing RILD issue's, kernel issue's and other stuff.
soo...maybe m wrong (has been a while snce ive ported) but im goin to drop a few lines anyhow......
porting is very different from source building.....the only reason you would need to dl the cm sources would be to compile the rom using sources...and right now the note 4 has none we would need device,kernel,common,vendor sources for that....so... we cant source build right now only port....sp what we need to do is research which device officially or unofficially that has cm with same specs as the note4 things like screen size, board, things of that nature....and would highly recommend using the same carrier as well.....but once we have that info....dl that phones cm rom zip....dl one of our phones rom zips.....now for the fun....ill lay out a way i did it maybe is the same still ...
place both cm zip and note 4 zip on desktop..
create a new folder call it new
drag all files from the cm zip into the new
open the new and open the note 4 zip have them side by side
now your going to drag pretty much all folders/files from the note 4 system folder into the new sytsem folder one folder at a time excluding:
app,priv-app,etc,fonts,media,framework,xbin (im probably forgetting one or two but has been a long time)
now the fun begins....time to edit some xmls and trial and error on pretty much everything until it is working right
you are also going to want to change out the kernel and have to edit the updater-script in the meta-inf....
im positive im forgetting a few things but this is pretty much what i can remember......from off the top of my head...some of the guides ill link in a bit will go into greater detail and explain things more in depth
a few links ive had bookmarked that will help ya
http://forum.xda-developers.com/showthread.php?t=1908008
http://forum.xda-developers.com/showthread.php?t=732957
http://forum.xda-developers.com/showthread.php?t=1957219
http://forum.xda-developers.com/showthread.php?t=1272270
http://forum.xda-developers.com/showthread.php?t=2113479
http://forum.xda-developers.com/showthread.php?t=1801690
http://forum.xda-developers.com/showthread.php?t=2251719
http://forum.xda-developers.com/showthread.php?t=1941239
http://forum.xda-developers.com/showthread.php?t=1805408
http://forum.xda-developers.com/showthread.php?t=2058850
all of these links in one way or another have helped me during my porting phase hope they do the same for you ...like ive said before im more of a source builder so thats what imgoing to be trying to do is getting a working tree... but if you need help just hit me up ill do what i can
Shouldn't this thread be in general?
jdidtht said:
Shouldn't this thread be in general?
Click to expand...
Click to collapse
yes it really should being as there is no development only discussion...but thats the moderators job not mine
spleef said:
yes it really should being as there is no development only discussion...but thats the moderators job not mine
Click to expand...
Click to collapse
Threads regarding R&D belong in development, so I guess it really belongs here. Even more so cause if it's moved to general, tons of n00bs will join in and destroy the thread. please keep this developers only.
Anyway thanks to see you join in Spleef, much appreciated !! Still setting up my environment myself ...
spleef said:
soo...maybe m wrong (has been a while snce ive ported) but im goin to drop a few lines anyhow......
porting is very different from source building.....the only reason you would need to dl the cm sources would be to compile the rom using sources...and right now the note 4 has none we would need device,kernel,common,vendor sources for that....so... we cant source build right now only port....sp what we need to do is research which device officially or unofficially that has cm with same specs as the note4 things like screen size, board, things of that nature....and would highly recommend using the same carrier as well.....but once we have that info....dl that phones cm rom zip....dl one of our phones rom zips.....now for the fun....ill lay out a way i did it maybe is the same still ...
place both cm zip and note 4 zip on desktop..
create a new folder call it new
drag all files from the cm zip into the new
open the new and open the note 4 zip have them side by side
now your going to drag pretty much all folders/files from the note 4 system folder into the new sytsem folder one folder at a time excluding:
app,priv-app,etc,fonts,media,framework,xbin (im probably forgetting one or two but has been a long time)
now the fun begins....time to edit some xmls and trial and error on pretty much everything until it is working right
you are also going to want to change out the kernel and have to edit the updater-script in the meta-inf....
im positive im forgetting a few things but this is pretty much what i can remember......from off the top of my head...some of the guides ill link in a bit will go into greater detail and explain things more in depth
a few links ive had bookmarked that will help ya
http://forum.xda-developers.com/showthread.php?t=1908008
http://forum.xda-developers.com/showthread.php?t=732957
http://forum.xda-developers.com/showthread.php?t=1957219
http://forum.xda-developers.com/showthread.php?t=1272270
http://forum.xda-developers.com/showthread.php?t=2113479
http://forum.xda-developers.com/showthread.php?t=1801690
http://forum.xda-developers.com/showthread.php?t=2251719
http://forum.xda-developers.com/showthread.php?t=1941239
http://forum.xda-developers.com/showthread.php?t=1805408
http://forum.xda-developers.com/showthread.php?t=2058850
all of these links in one way or another have helped me during my porting phase hope they do the same for you ...like ive said before im more of a source builder so thats what imgoing to be trying to do is getting a working tree... but if you need help just hit me up ill do what i can
Click to expand...
Click to collapse
Great addition to the thread ! Hmm I haven't done any porting myself. I figured once we have a kernel up (compiling it should be easy), then what's stopping us from booting CM ? I mean of course RILD won't work if we don't have a JNI (or what's it called on ART, ANI ? ) interface to the modem. Of course we won't have NFC, internet, telephony, all that. But merely booting a graphical interface that should be doable with Nexus 6 source code, right ? I mean all we need is SoC sources so we have cpu & graphics working, right ? So That was what I had in mind myself but your approach actually is quite the same now I think of it
Thread is moved to general AGAIN. Hehe. Starting a development thread ON XDA and have it in the developer section seems harder than porting CM12 Anyway I guess it doesn't matter in which section it is, as long as n00bs and trolls stay out and we can focus on development only.
Anyway, downloading kernel sources as we speak ...
BTW, here is Nexus 6 source code: http://www.xda-developers.com/android/google-nexus-6-factory-images/
Going to down that right now too ...
Ok, building kernel as we speak. I just installed the arm-eabi-4.7 toolchain, like this:
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/
And then edited the makefile and issued the 3 commands all as specified in README_Kernel.txt from the Samsung Kernel. So far so good
And yes, as expected, build breaks:
drivers/scsi/ufs/ufs_test.c:25:19: fatal error: ../sd.h: No such file or directory
compilation terminated.
make[3]: *** [drivers/scsi/ufs/ufs_test.o] Error 1
make[2]: *** [drivers/scsi/ufs] Error 2
make[1]: *** [drivers/scsi] Error 2
make: *** [drivers] Error 2
Hehe, Samsung wouldn't be Samsung if they would supply a kernel that actually builds from the start Going to investigate ...
Actually that seems like an easy fix, just linked the file correctly
And a new break:
In file included from drivers/gud/MobiCoreDriver/logging.c:21:0:
drivers/gud/MobiCoreDriver/main.h:24:22: fatal error: platform.h: No such file or directory
I'd say it's looking for the file in platforms/MSM8960_SURF_STD, going to link it correctly ...
And building again ...
n file included from drivers/video/msm/mdss/mdss_mdp_trace.h:255:0,
from drivers/video/msm/mdss/mdss_mdp.c:61:
include/trace/define_trace.h:79:43: fatal error: ./mdss_mdp_trace.h: No such file or directory
Include should point to kernel includes, fixing it again
And building again ...
Code:
OBJCOPY arch/arm/boot/Image
Kernel: arch/arm/boot/Image is ready
LZO arch/arm/boot/compressed/piggy.lzo
AS arch/arm/boot/compressed/piggy.lzo.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
Kernel ready Of course that was the easy part, hehe, but still, progress. Tomorrow going to start with the difficult part, getting CM up
I've ported before but only tw where it was mainly framework edits. Never worked with cm before but like the op I'm keen to learn. If i can help at all just let me know, I use linux mint myself rather than Ubuntu but they're very similar
So, just downloaded Nexus 6 sources. It seems that directory /device/moto/shamu contains the device hardware stuff we need ! Going to research some more today ...
*EDIT* also mind the propietary-blobs.txt in that directory. I'm still waiting for my Note 4 myself (hopefully friday), but this needs to be compared with the files on the device, cause if they exist, they will be blobs of course and we need them.
Hi everybody. I was trying to make work XOSP for our device. Even after the hard work of @nitin.chobhe, who did everything (really great job, man. Always thanks for all your work), there are various problem. First of all SIM card. I flashed the zip and SIM card is not recognized. I searched about it and I discovered that it's a common problem using cm repos in local_manifest, which are no longer updated. I saw @[email protected] and other devs solved with @temasek help. So he tried with temasek's repos, but he get this error:
Code:
device/samsung/hlte-common/gps/core/loc_core_log.cpp:134:15: error: constant expression evaluates to 4294967295 which cannot be narrowed to type 'long' [-Wc++11-narrowing]
Another problem is sdcard. It works, but media files on it are not automatically recognized, but if you open a file in sdcard, it being open.
There is also sound crack, but I think that it's the most easy to fix. I'll try flashing the audio-policy zip.
As for now these are the biggest bugs. I'll keep the thread updated. Again, thanks to @nitin.chobhe for his great work and support.
Ivan
EDIT 23 June 2016 - 11.27: Changing hlte-common repos back to cm's one it seems it worked. Dunno the final result. By the way audio problem is fixed, as I thought it was a problem with audiopolicy.so. Changed with Samsung's one and now sounds great.
EDIT 23 June 2016 - 12.18: Good news and bad news. Camera is fixed, battery life is alot better, phone is very smooth, no other heat problems, but SIM still doesn't work. EFS restore from TWRP didn't work. Will try some other methods.
EDIT 23 June 2016 - 12.36: Nothing to do. Even flashing latest modem and bootloader SIM is not recognised. I give up. Hope some other devs keep the project alive. Greetings
LuckyNuke1310 said:
Hi everybody. I was trying to make work XOSP for our device. Even after the hard work of @nitin.chobhe, who did everything (really great job, man. Always thanks for all your work), there are various problem. First of all SIM card. I flashed the zip and SIM card is not recognized. I searched about it and I discovered that it's a common problem using cm repos in local_manifest, which are no longer updated. I saw @[email protected] and other devs solved with @temasek help. So he tried with temasek's repos, but he get this error:
Another problem is sdcard. It works, but media files on it are not automatically recognized, but if you open a file in sdcard, it being open.
There is also sound crack, but I think that it's the most easy to fix. I'll try flashing the audio-policy zip.
As for now these are the biggest bugs. I'll keep the thread updated. Again, thanks to @nitin.chobhe for his great work and support.
Ivan
EDIT 23 June 2016 - 11.27: Changing hlte-common repos back to cm's one it seems it worked. Dunno the final result. By the way audio problem is fixed, as I thought it was a problem with audiopolicy.so. Changed with Samsung's one and now sounds great.
EDIT 23 June 2016 - 12.18: Good news and bad news. Camera is fixed, battery life is alot better, phone is very smooth, no other heat problems, but SIM still doesn't work. EFS restore from TWRP didn't work. Will try some other methods.
EDIT 23 June 2016 - 12.36: Nothing to do. Even flashing latest modem and bootloader SIM is not recognised. I give up. Hope some other devs keep the project alive. Greetings
Click to expand...
Click to collapse
You can still post a alpha version and take ur time to solve the issue
techdude18 said:
You can still post a alpha version and take ur time to solve the issue
Click to expand...
Click to collapse
Well, unfortunately I don't have that build anymore, and btw now it's obsolete. Moreover, I don't have neither my Note 3 nor my building setup anymore. I'm now happy with OnePlus 3, where all the correct sources are out, and there are never problems compiling. Samsung devices are not that good for building cm-based ROMs IMHO, surely not for XOSP. I asked a famous dev in Note 3 CM section (I don't want to write his name) to try to compile it, and he said me he did, but he never released it (and maybe he never compiled it too), and he never answered my pm anymore. XOSP could be a great ROM for Note 3, but nobody cares about it, unfortunately
Hope someone will think about it.