Related
Hi I have found the way to port ICS to the galaxy players. :
http://www.freeyourandroid.com/guide/compile-ics
The problem is that I can't find the binaries for the galaxy player. Where I can find them?
arent they located in /system/bin?
Need root first though
(I would help out with this, but dont really know how to do it, and i dont have the player yet)
zaclimon said:
Hi I have found the way to port ICS to the galaxy players. :
http://www.freeyourandroid.com/guide/compile-ics
The problem is that I can't find the binaries for the galaxy player. Where I can find them?
Click to expand...
Click to collapse
Will this actually boot and run? If it's that "easy", then why don't more devices have ICS? If you can extract the binaries and cook up a rom, I would be happy to test it . Also, if I have time later this week, I'll try to follow those instructions and then post my results. If everything works on the first try, I'll be very surprised but not at all dissapointed . Thanks for sharing this
Dyskmaster said:
Will this actually boot and run? If it's that "easy", then why don't more devices have ICS? If you can extract the binaries and cook up a rom, I would be happy to test it . Also, if I have time later this week, I'll try to follow those instructions and then post my results. If everything works on the first try, I'll be very surprised but not at all dissapointed . Thanks for sharing this
Click to expand...
Click to collapse
Well maybe because people don't know how to do it. And as for the current rom the major problem is the hardware acceleration and the camera. Maybe We can find it (The binairies) at opensource.samsung.com
It should be easier than phones because you don't have to worry about not screwing with voice, data, and stuff like that. Just get it on and get all the apps working correctly. Radios are always the hardest.
I've also been triyng to compile the source for the player but i wasnt able to do so, the thing is that the source compiles fine with the pre-adjustments it comes with, i mean the androidboard.mk ( i think thats the name of the file not sure), but when i changed the variables for a armv5 build, which is the core of the device and the ones that comes in the same file on the opensource.samsung soource, it just doesnt compile and throws some kind of errors about some libraries that i didnt touched. i dont know what i had been doing wrong.
I Also found this video in which they show whats in every folder, and how to build and add packages from source to the build:
http://marakana.com/forums/android/general/269.html
This is a detail process description from the official android site to build from source, very similar like the one zaclimon found:
http://source.android.com/source/initializing.html
The source from samsung doesnt have all the drivers, just the alsa audio driver, i guess we gonna have to find a way to get the binaries like cyanogen did, maybe get some scripts they use and try to do it ourselves:
http://wiki.cyanogenmod.com/wiki/Sa...le_CyanogenMod_(Linux)#Copy_proprietary_files
it is done through the adb, but the thing is to get those files, maybe we could ask that fellow some help for this step, since he has the experience.
sodomywar said:
I've also been triyng to compile the source for the player but i wasnt able to do so, the thing is that the source compiles fine with the pre-adjustments it comes with, i mean the androidboard.mk ( i think thats the name of the file not sure), but when i changed the variables for a armv5 build, which is the core of the device and the ones that comes in the same file on the opensource.samsung soource, it just doesnt compile and throws some kind of errors about some libraries that i didnt touched. i dont know what i had been doing wrong.
I Also found this video in which they show whats in every folder, and how to build and add packages from source to the build:
http://marakana.com/forums/android/general/269.html
This is a detail process description from the official android site to build from source, very similar like the one zaclimon found:
http://source.android.com/source/initializing.html
The source from samsung doesnt have all the drivers, just the alsa audio driver, i guess we gonna have to find a way to get the binaries like cyanogen did, maybe get some scripts they use and try to do it ourselves:
http://wiki.cyanogenmod.com/wiki/Sa...le_CyanogenMod_(Linux)#Copy_proprietary_files
it is done through the adb, but the thing is to get those files, maybe we could ask that fellow some help for this step, since he has the experience.
Click to expand...
Click to collapse
The core is a ARMv7 right? because the hummingbird processor is a ARMv7. Maybe it did failed because of that? I found the gpu drivers from the opensource. Check in the kernel folder. If I can give you the gpu file if you want. Well tell me what files you are missing i'll find to give it to you. (Well I don't know how to program so I try do to my best.)
EDIT: Also its seem that to compile ICS is more difficult than the other versions. We do need ubuntu to extract the binaries right?
EDIT2: People are saying that it's easier to build from CM9 than from the source. It is right or it's the same thing?
http://forum.cyanogenmod.com/topic/38960-build-your-own-cm9ics-preview-on-ubuntu-and-perhaps-debian/
Galaxy S Phone
Shouldn't you just be able to modify a Galaxy S ICS port and take out the data and other stuff you don't need?
zaclimon said:
The core is a ARMv7 right? because the hummingbird processor is a ARMv7. Maybe it did failed because of that?
Click to expand...
Click to collapse
Well, i configured it with the files of the samsung source, and it said ARMv5, we need to know which one it is, probably faild because of libaries compatibilities for that architecture.
zaclimon said:
EDIT: Also its seem that to compile ICS is more difficult than the other versions. We do need ubuntu to extract the binaries right?
EDIT2: People are saying that it's easier to build from CM9 than from the source. It is right or it's the same thing?
Click to expand...
Click to collapse
Maybe it is easier than the official source, they modify the source and takes out some things that cellphones dont need 'cause the source it's made for all devices, so it could be smaller and easier to compile, i'm gonna try this port and let ya' know, it will take a while since the source it's huge
Would be great if a couple of us do it, if you can @zaclimon try it, you don't need ubuntu, if you know which libaries that command has (sudo apt-get install build-essential). I have debian and i compiled the source just fine, debian has a minimal installation (no X11) but to compile source you dont need anything else! Let me know if anyone else it's triyng we could excahnge some ideas!
sodomywar said:
Well, i configured it with the files of the samsung source, and it said ARMv5, we need to know which one it is, probably faild because of libaries compatibilities for that architecture.
Maybe it is easier than the official source, they modify the source and takes out some things that cellphones dont need 'cause the source it's made for all devices, so it could be smaller and easier to compile, i'm gonna try this port and let ya' know, it will take a while since the source it's huge
Would be great if a couple of us do it, if you can @zaclimon try it, you don't need ubuntu, if you know which libaries that command has (sudo apt-get install build-essential). I have debian and i compiled the source just fine, debian has a minimal installation (no X11) but to compile source you dont need anything else! Let me know if anyone else it's triyng we could excahnge some ideas!
Click to expand...
Click to collapse
how many MB or GB the source has because I can't exceed my download's limitations?
EDIT: I'm a linux newbie. Is Ubuntu is the same thing as debian? Because Ubuntu is debian based right?
EDIT2: nevermind I'll be using ubuntu
alltellmobile said:
Shouldn't you just be able to modify a Galaxy S ICS port and take out the data and other stuff you don't need?
Click to expand...
Click to collapse
I don't know if we can (we should ask permissions) but it's definitly possible.
zaclimon said:
EDIT: I'm a linux newbie. Is Ubuntu is the same thing as debian? Because Ubuntu is debian based right?
Click to expand...
Click to collapse
Yea Ubuntu should be pretty much the same.
Wish I knew how to program, because i would help out.
alltellmobile said:
Yea Ubuntu should be pretty much the same.
Wish I knew how to program, because i would help out.
Click to expand...
Click to collapse
You can help I follow the tutorials there:
http://www.freeyourandroid.com/guide/compile-ics
http://marakana.com/forums/android/general/269.html
Ok i was reading the first tutorial and got to the part about binaries for graphics acceleration; wouldn't we have to get ours before we compile it. Also i only have the US version of the galaxy player and if i made an image i couldn't test it because we don't have a custom recovery for ours.
alltellmobile said:
Ok i was reading the first tutorial and got to the part about binaries for graphics acceleration; wouldn't we have to get ours before we compile it. Also i only have the US version of the galaxy player and if i made an image i couldn't test it because we don't have a custom recovery for ours.
Click to expand...
Click to collapse
Oh that's true well you can try to port a custom recovery?
zaclimon said:
Oh that's true well you can try to port a custom recovery?
Click to expand...
Click to collapse
HaHa I'm not that good. that sounds way more complicated
hey guys, i've been following this thread and hopefully i can be of some help...
i'm currently in the process of pulling the system files from the original gingerbread build from the SGP...it looks like there will be some trial and error here comparing that of the nexus s build...correct me if i'm wrong, but is this where most of the proprietary libraries are located for the device?
i'm willing to engineer a generic build, described in the video tutorial and making the necessary adjustments for the ARMv7 board...
this is my first attempt at compiling Android source, so maybe we will have something or maybe i will have a good ol' brick...thanks for the great tutorial and video @zaclimon this has definitely shed some light on porting ICS for SGP
jdale38 said:
hey guys, i've been following this thread and hopefully i can be of some help...
i'm currently in the process of pulling the system files from the original gingerbread build from the SGP...it looks like there will be some trial and error here comparing that of the nexus s build...correct me if i'm wrong, but is this where most of the proprietary libraries are located for the device?
i'm willing to engineer a generic build, described in the video tutorial and making the necessary adjustments for the ARMv7 board...
this is my first attempt at compiling Android source, so maybe we will have something or maybe i will have a good ol' brick...thanks for the great tutorial and video @zaclimon this has definitely shed some light on porting ICS for SGP
Click to expand...
Click to collapse
Yes they are supposed to be there. But I have download all the source code of the firmware from opensource.samsung.com
Me and sodomywar are working with the internationnal version of the SGP4. If you want to join you're welcome.
EDIT: No problem for the tutorials.
alltellmobile said:
HaHa I'm not that good. that sounds way more complicated
Click to expand...
Click to collapse
Google is your friend
So this is where i'm at currently. I'm trying to compile and I got this error:
Code:
build/core/base_rules.mk:166: *** system/extras/ext4_utils: MODULE.TARGET.EXECUTABLES.setup_fs already defined by device/samsung/galaxyplayer. Stop.
Does anyone know how to remove that error?
EDIT: nvm I managed to remove this error.
WANTED: Users to port SGS roms to the 4.0. You will need to know how to complete a full restore if something goes wrong, but that's it. I cannot go through the forums searching for good SGS roms, as I have several threads to manage, and a rom to work on. The steps are easy for you though, and if you port a rom I will add it in the OP.
First of all, I want to say that I take NO credit on any of these roms. All I did was port them over and add speed tweaks, or added ones that users have ported. If the rom creators or mods have any issue whatsoever with this thread, I will happily take it down, even though I think it would be a large contribution to the 4.0 community. I will continue to update this forum with info as I go along.
I, after a fortunate afternoon of boredom, have managed to successfully begin porting I9000 roms to our devices! Fortunately, they are similar enough that it boots without any modifications. I will put up here any ports that I make, and any that the users create. Note that these WILL NOT BE UPDATED! These are one-time ports, to be used and improved upon by the community. Anything that is broken now will stay broken, unless a user decides to fix/update it, then I will include it in the OP.
What *should* work in all ported roms:
wifi
GPS
home buttons
everything else
What will probably *not* work on ported roms:
Bluetooth
Camera
backlight on buttons
Ported roms:
~GamerzRom odexed V11-~
Link to original thread: http://forum.xda-developers.com/showthread.php?t=1656081
Added:
V6 supercharger, and build.prop tweaks from it.
init.d tweaks from my rom
ext4 filesystem
Advanced mount options
Auto zipalign and Database optimize
Removed apps that do not work on our Player (such as the Dialer)
Download:http://www.mediafire.com/download.php?ctuu2w295w2xlk6
~Saurom~
Original thread:http://forum.xda-developers.com/showthread.php?t=1388342
Ported download link:http://www.mediafire.com/download.php?csua40hkg1r3m86
~JellyBeanRom~
Original thread: http://forum.xda-developers.com/showthread.php?t=1260709&highlight=gb
Ported download link:http://www.mediafire.com/download.php?mgec81f3ifck221
~Ario Rom (ported by ChaosChris)~
Ported thread link : http://forum.xda-developers.com/showthread.php?p=29950015#post29950015
Original thread: http://forum.xda-developers.com/showthread.php?t=1536558
To use these Roms:
You MUST use a Gplayer kernel! GT-I9000 kernels will not boot!
A full wipe may be necessary with some roms if you encounter issues.
Converting (for porters)
Steps:
1. Download wanted rom (must be GB)
2.Move the zip to the internal sdcard
3.Reboot into recovery
4.Flash zip, then boot into download mode
5.Flash a SGP kernel
6. apply my mod pack to the rom, by either copying/pasting the system directory over the SGS rom's system directory, or by pushing it via adb, (eg. adb push /path/to/modpack /system).
7. Profit!
NOTE: after applying this, porters may want to remove non-working packages such as the dialer and mms, as they may cause issues with the end result if they are kept in. Do not delete phone.apk though!! This is required for the camera and some other things, and breaks stuff on certain roms. You have been warned.
NOTE: If you use this modpack, please give me credit, and link back to this thread so that more people can use it. Also, you should probably link back to the ported rom's thread as well, to avoid "ripping off" those devs.
Modpack:
Changelog
V1-
Preliminary release
Fixes wifi and GPS
Includes v6 supercharger and init.d tweaks
V2-
fixed vold.fstab so sdcard is mounted properly.
Download:
ModpackV1:
http://www.mediafire.com/download.php?diaq6im4i18ktf7
NOTE:Note that this is preliminary. It fixes everything listed, and attempts to fix some broken things. Your mileage may vary. This is not a cwm flashable zip! you much extract and adb push this over the existing system directory. This is mainly intended for porters, so users apply at your own risk. This will work, but is a very early release.
Modpack V2 (thanks to ChaosChris):
https://docs.google.com/open?id=0B9OVlH2Pl76DZk5Pa3lJVXlrYzA
Looking good! Does the gamerz port have the 388mb of ram, I thought that was kernal related?
Sent using Tapatalk
iJimaniac said:
Looking good! Does the gamerz port have the 388mb of ram, I thought that was kernal related?
Sent using Tapatalk
Click to expand...
Click to collapse
Yeah, it says that because it includes semaphore's kernel, which raises the max rom to 380, which we could do on our kernel's, but apparently that breaks a lot of stuff if you go much further then 350 (according to klin).
is the wifi fixed in your port or do we have to do your fix after flashing?
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Supermaster34 said:
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Click to expand...
Click to collapse
check over in the operation: ics for the 4.0 thread I believe they are already attemping to use the cm7 kernel to boot a cm9.
daniel644 said:
is the wifi fixed in your port or do we have to do your fix after flashing?
Click to expand...
Click to collapse
Yeah, it is fixed before you flash. Once I manage to iron out a few more bugs, I will probably release a "conversion pack" that fixes all the issues. I already have one that fixes wifi and gps, but bluetooth and camera have me stumped, and I do not want to replace the entire hw/lib folder, because some of these roms have lib optimizations, but I may have to.
Sent from my GT-I9000 using xda app-developers app
Supermaster34 said:
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Click to expand...
Click to collapse
Since I am merely redistributing their work, not incorporaring it into anything I have made, or taking any credit for it, I don't asking permission is necessary. I may be completely off base, but I think that as long as you give devs 100% credit, and link to their original work, it is okay. It may not be the best option, but neither is asking EVERY dev if I can port their rom, or ask permission for user-ported roms.
Youay have an idea there, althouh I think that zaclimon has tried it, and he said it wouldn't boot. I have 2 efs backups, so I guess I can try, although even if the kernel boots, I bet I will have to do a LOT more work before it is usable. I also believe that he said the issues may have been rom based, so here it goes, and wish me luck.
Sent from my GT-I9000 using xda app-developers app
hanthesolo said:
Since I am merely redistributing their work, not incorporaring it into anything I have made, or taking any credit for it, I don't asking permission is necessary. I may be completely off base, but I think that as long as you give devs 100% credit, and link to their original work, it is okay. It may not be the best option, but neither is asking EVERY dev if I can port their rom, or ask permission for user-ported roms.
Youay have an idea there, althouh I think that daniel has tried it, abd he said it wouldn't boot. I have 2 efs backups, so I guess I can try, although even if the kernel boots, I bet I will have to do a LOT more work before it is usable.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
I've already tried with a cm7 kernel and I got an error of looping (netd1.0 starting) that's why I'm trying to do something. Now I need to backport 3.0.8 usb gadget drivers.
zaclimon said:
I've already tried with a cm7 kernel and I got an error of looping (netd1.0 starting) that's why I'm trying to do something. Now I need to backport 3.0.8 usb gadget drivers.
Click to expand...
Click to collapse
Whoops, I meant you . I will try with a official cm9 build from the SGS forums, and see if that fares any better. Probably will not, but it doesn't hurt to try.
EDIT: well, nevermind about that. He seems to have pulled all of his download links, and I cannot get to the CM7 build. Oh well...
I am going to try anyway with the I9000 package since it seems to have EXT4 support, and I *think* that was what was bootlooping me earlier. This as all just my hopeful rationalization, of course . A lot farther out there, but maybe I can use a SGP5.0 kernel to get it booting. A LOT less likely, but hey, i'm experimenting .
EDIT: I cannot try ICS, since I need to reboot into recovery a second time, and I cannot do that, as I have the intl bootloader on my US device, and it would require it to be booting first.
hanthesolo said:
Whoops, I meant you . I will try with a official cm9 build from the SGS forums, and see if that fares any better. Probably will not, but it doesn't hurt to try.
EDIT: well, nevermind about that. He seems to have pulled all of his download links, and I cannot get to the CM7 build. Oh well...
I am going to try anyway with the I9000 package since it seems to have EXT4 support, and I *think* that was what was bootlooping me earlier. This as all just my hopeful rationalization, of course .
Click to expand...
Click to collapse
I think we should do like entrophy's because I get bored from mtd. Also just tried the gamerz rom port. As I see the camera works, don't know about bluetooth (it can turn on). Vibration works too. I was able to connect to wifi pretty fast and I have one word for this rom. FAST!!!!
Good job!!
zaclimon said:
I think we should do like entrophy's because I get bored from mtd. Also just tried the gamerz rom port. As I see the camera works, don't know about bluetooth (it can turn on). Vibration works too. I was able to connect to wifi pretty fast and I have one word for this rom. FAST!!!!
Good job!!
Click to expand...
Click to collapse
Well, thet camera shows a preview, but fails when a pic is taken, for some reason. Bluetooth does turn on, but is not seen by any other devices, and cannot scan for others either. I did do a little tweaking with Gamerz, so it will be even faster than it was already, which is pretty blazing! I have 2 more that I can put up (I have a preliminary package that I just adb push over the system files that works for now). I have also gotten the camera apk onto my rom, and it works really well! It doesn't take 5 MP pics, or record 720p video (which may be because I am using Terrasilent, which reduces the amount of Vram the system can have), but tap to autofocus and everything else works pretty well. I have a sneaking suspicion that the camera is soft limited, not hard-limited.
I also noted that the external sd card isn't working too (a problem with vold.fstab I'll correct it right now)
zaclimon said:
I also noted that the external sd card isn't working too (a problem with vold.fstab I'll correct it right now)
Click to expand...
Click to collapse
I don't use an externel sdcard, so thanks for pointing that out! I will include a fixed version in my mod pack.
hanthesolo said:
I don't use an externel sdcard, so thanks for pointing that out! I will include a fixed version in my mod pack.
Click to expand...
Click to collapse
Here's the vold.fstab if you need it
Okay, it seems that the zip hosed my partitions (converted them to yaffs2 and mtd), so I am going to perform a full restore, and just keep porting GB roms. As soon as you can get the usb gadget driver working, zaclimon, I guess I can keep working on it, but for now I will just keep to GB.
Two more roms up! I will probably not port any other unless I see an especially good one, but I will put up my mod pack tomorrow.
has anyone found out if the ported roms enable tv out or has someone found out if tv out support is in the i9000 kernal?
TV out has to have hardware, or your not going anywhere. I think the galaxy player lacks the hardware unfortunately. If it does have the hardware, it was very dumb of Samsung not to enable it.
Sent using Tapatalk
iJimaniac said:
TV out has to have hardware, or your not going anywhere. I think the galaxy player lacks the hardware unfortunately. If it does have the hardware, it was very dumb of Samsung not to enable it.
Sent using Tapatalk
Click to expand...
Click to collapse
what hardware does the galaxy s i9000 have that allows for tv out? I thought the galaxy s i9000 and the galaxy player 4.0 had the same gpu?
http://forum.xda-developers.com/showthread.php?t=991276
Devs, can anyone look into if this could be good use to our prime?
I Dont have much time to look into this, but hopefully someone capable will..
This was implanted in the WSG rom (now discontinued), from what I saw, it did help a lot, everything became smoother compared to the stock rom.
I tried v6 supercharger on my LG Optimus 2x and it made the difference. Would it be dangerous trying it on a simply rooted TFP on stock?
jason1993 said:
I tried v6 supercharger on my LG Optimus 2x and it made the difference. Would it be dangerous trying it on a simply rooted TFP on stock?
Click to expand...
Click to collapse
No, just don't set Script Manager to run it on boot until you've confirmed that it works. There's nothing to lose.
ZebTheCalvinist said:
No, just don't set Script Manager to run it on boot until you've confirmed that it works. There's nothing to lose.
Click to expand...
Click to collapse
Yeah it would be nice to have this running on stocked, rooted primes untill better updates come out.
From what i understand you have to de compile service.jar and edit a file in there.
Re pack the file n replace the original service.jar with it
Then run the supercharge script.
Doesnt seem to be too complicated.
I will def be looking into this when i have the time, was just hoping someone with better knowledge can look into this sooner.
alanhzl said:
Yeah it would be nice to have this running on stocked, rooted primes untill better updates come out.
From what i understand you have to de compile service.jar and edit a file in there.
Re pack the file n replace the original service.jar with it
Then run the supercharge script.
Doesnt seem to be too complicated.
I will def be looking into this when i have the time, was just hoping someone with better knowledge can look into this sooner.
Click to expand...
Click to collapse
That is all you have to do. I personally use it on all of my devices. I would attach my services.jar for you but I'm not 100% sure the one on Wookie will be identical. It is a pretty painless process but if you need any assistance send me a pm.
ZebTheCalvinist said:
No, just don't set Script Manager to run it on boot until you've confirmed that it works. There's nothing to lose.
Click to expand...
Click to collapse
Really? No file system managed at all?
alanhzl said:
Yeah it would be nice to have this running on stocked, rooted primes untill better updates come out.
From what i understand you have to de compile service.jar and edit a file in there.
Re pack the file n replace the original service.jar with it
Then run the supercharge script.
Doesnt seem to be too complicated.
I will def be looking into this when i have the time, was just hoping someone with better knowledge can look into this sooner.
Click to expand...
Click to collapse
Is it necessary that work on the service.jar? I've always run supercharger without it, simply using terminal emulator.
jason1993 said:
Really? No file system managed at all?
Is it necessary that work on the service.jar? I've always run supercharger without it, simply using terminal emulator.
Click to expand...
Click to collapse
as the tutorial suggested (from the original dev thread), post ICS roms has the app's "priority"(for lack of better explanation) built-in to service.jar.
so unless you are running a deodex rom (which is not the case for our stock prime), you will have to re-compile service.jar in order to take full
benefit of this super charge script.
i think i will try to looking to it tonight, to see if i can get something going lol. i'm no dev by any mean.
alanhzl said:
as the tutorial suggested (from the original dev thread), post ICS roms has the app's "priority"(for lack of better explanation) built-in to service.jar.
so unless you are running a deodex rom (which is not the case for our stock prime), you will have to re-compile service.jar in order to take full
benefit of this super charge script.
i think i will try to looking to it tonight, to see if i can get something going lol. i'm no dev by any mean.
Click to expand...
Click to collapse
I'll upload a modified odexed service.jar if someone provides me with one.
Sent from my SGH-I747 using Tapatalk 2
Not sure on the purpose of the OP .
has he even tried it on the prime?
i've been using this for a while now and it works fine.
Just try it rather than requesting Dev help.
jiffy1080 said:
I'll upload a modified odexed service.jar if someone provides me with one.
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
And what can we do with that modified odexed service.jar? Replace the stock one with the modified one?
Sent from my Transformer Prime TF201 using xda premium
After reading more into the tutorial, i think that the script that the original supercharge dev is providing has the service.jar patching included.
Meaning we dont have to manually edit the file etc etc, just run the script and everything is automated.
But i 'm not comfortable of running the script on my prime, as mine is locked and i have no way of creating a backup incase something go south and i
Ended up with a boot loop....
So i guess if anyone has done this on their locked prime with success, please post and share, sorry for calling for devs, as i initially thought this
Would involved some modification to system files..
P.s. i'm by no mean trying to encourage anyone to run this if they are not comfortable, just that i havent seen anyone bring this up, and thought it may
Be able to give our primes a little bit more boost if confirmed that is safe and working.
alanhzl said:
After reading more into the tutorial, i think that the script that the original supercharge dev is providing has the service.jar patching included.
Meaning we dont have to manually edit the file etc etc, just run the script and everything is automated.
But i 'm not comfortable of running the script on my prime, as mine is locked and i have no way of creating a backup incase something go south and i
Ended up with a boot loop....
So i guess if anyone has done this on their locked prime with success, please post and share, sorry for calling for devs, as i initially thought this
Would involved some modification to system files..
P.s. i'm by no mean trying to encourage anyone to run this if they are not comfortable, just that i havent seen anyone bring this up, and thought it may
Be able to give our primes a little bit more boost if confirmed that is safe and working.
Click to expand...
Click to collapse
Maybe you can recover from a potential bootloop could by installing the whole original firmware via the sdcard method. It could be done, right?
Sent from my Galaxy Nexus using xda premium
jason1993 said:
Maybe you can recover from a potential bootloop could by installing the whole original firmware via the sdcard method. It could be done, right?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I m not sure.. it maybe possible.
jiffy1080 said:
That is all you have to do. I personally use it on all of my devices. I would attach my services.jar for you but I'm not 100% sure the one on Wookie will be identical. It is a pretty painless process but if you need any assistance send me a pm.
Click to expand...
Click to collapse
Thanks jiffy for trying to help, is your prime locked and do u currently have super charge running?
alanhzl said:
I m not sure.. it maybe possible.
Click to expand...
Click to collapse
When i first rooted my prime i uninstalled some system apps (asus's bloatware) and, since i wasn't able to update to .21 (dead droid screen during the installation) i did a factory reset: during setup configuration, at one point, after signing in my google account, setup configuration force closed everytime, so i had to send it to Asus to fix. After i had RMAed it, somebody suggested me the update from sd trick. So i think (but i'm not 100% sure) that if that trick can work without system apps it should also work with managed system files, since it doesn't matter your system at all.
Sent from my Galaxy Nexus using xda premium
I used it only prime with the virtuous prime ROM. It made it just that much better.
Sent from my Transformer Prime TF201 using xda app-developers app
Hey guys, my question is essentially what the title says. I find that in CM10 based roms, that whenever I use the stock cyanogen mod browser, it automatically goes into desktop mode (and is stuck there. The desktop mode checkbox, however, is unchecked.) I'm fairly sure it worked before I used the touch pad fix here - http://forum.xda-developers.com/showthread.php?t=1893343 - So I think it might be a framework/build.prop issue, but I'm not sure. I've been looking to fix this problem everywhere but haven't really been able to find a solution. Do you guys have any idea what the fix might be?
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
smokerman said:
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
Click to expand...
Click to collapse
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
fishvtt said:
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
Click to expand...
Click to collapse
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Hey, smokerman, would you know how to mess with .jar files. I kinda want to go exploring to see if I can do anything.
you have here a simple guide by @CriGiu
http://forum.xda-developers.com/showthread.php?t=2322231
could help you.:good:
fishvtt said:
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
Click to expand...
Click to collapse
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
Oh ok, I'll try testing that out.
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
All right, well that seems to do the trick. When I try to use the touchpad activator app, it gives me the "error 5 expected reciever of type android.view.ViewRoot, but got android.view.ViewRootImpl". But, Dead Trigger works perfectly how it's supposed to, and the stock browser is using the mobile version now. Just remember to make the necessary build.prop changes as outlined in Fahrenheit's guide.
I have the ZTE Avail 2 (aka Z992) (and it sucks, considering it's a $70 phone, buying a new one isn't an option because I just built a computer). It hasn't had an update since 4.1.1 and it's very slow, (usually have only ~50mb of ram free when just sitting at launcher) even with all of the tricks to speed it up (greenfiy, cleaner, etc) and on top of that, it's loaded with features that ZTE put in that suck. So after searching and searching for a custom ROM with support for my phone, I can confirm there is zero. I looked at the rom dev tutorial - http://forum.xda-developers.com/showthread.php?t=1272270 and the kitchen program doesn't support my phone either. Does that mean I'm screwed? If there's a way to make a rom compatible other than the android kitchen or straight up learning to program, please tell me. I'm willing to learn anything that isn't hugely time consuming. Thanks for any replies.
FourZer0 said:
Does that mean I'm screwed? If there's a way to make a rom compatible other than the android kitchen or straight up learning to program, please tell me. I'm willing to learn anything that isn't hugely time consuming. Thanks for any replies.
Click to expand...
Click to collapse
No, you are not. You can try many other porting tutorials around the web. I found a list of phones similar to yours, might come in handy.
In fact, since your are trying to "port" ROMs, just think about the fact that "where did those ROMs come from?" Those ROMs were built from source code. The Android project is open source and if you are feeling adventurous, you can just grab the source code and compile it yourself for your device. It might be very easy or very tough, depending on your device. I would advise you to try to build Cyanogenmod 10.1 from source code. Check here and here.
And make sure to check this (must).
Cheers man! Trust me, trying to build Cyanogenmod from source will be a lot of fun!
Thank you! So I found CM for the xperia tipo, which was on the list of similar devices. I should use that one and change whatever needs to be changed, right?
Also, is it possible to do that for 4.4 stock? That may be a better idea if CM consumes too much ram
tuxboy said:
No, you are not. You can try many other porting tutorials around the web. I found a list of phones similar to yours, might come in handy.
In fact, since your are trying to "port" ROMs, just think about the fact that "where did those ROMs come from?" Those ROMs were built from source code. The Android project is open source and if you are feeling adventurous, you can just grab the source code and compile it yourself for your device. It might be very easy or very tough, depending on your device. I would advise you to try to build Cyanogenmod 10.1 from source code. Check here and here.
And make sure to check this (must).
Cheers man! Trust me, trying to build Cyanogenmod from source will be a lot of fun!
Click to expand...
Click to collapse
Okay, ignore my last replies, I've been reading a lot and kind of know what I'm doing now.
Only problem is, I can't find a stock rom of my phone! The closest thing I found was a custom ROM for a phone similar to mine, which is confirmed working to the one I actually have. So would that do okay? androidforums . com/prelude-all-things-root/795640-azazel-rom-z993-aio.html is the one. Thanks again for any help.
FourZer0 said:
Okay, ignore my last replies, I've been reading a lot and kind of know what I'm doing now.
Only problem is, I can't find a stock rom of my phone! The closest thing I found was a custom ROM for a phone similar to mine, which is confirmed working to the one I actually have. So would that do okay? androidforums . com/prelude-all-things-root/795640-azazel-rom-z993-aio.html is the one. Thanks again for any help.
Click to expand...
Click to collapse
You can easily take a backup of your current ROM. Try booting into recovery and making your own custom recovery (ClockWordMod).
tuxboy said:
You can easily take a backup of your current ROM. Try booting into recovery and making your own custom recovery (ClockWordMod).
Click to expand...
Click to collapse
Oh, I didn't know that would work, thanks again! I have my rom modded like crazy though, tons of xposed modules and build.prop edits, also I uninstalled a lot of stock apps - I'm sure I could get the build.prop somewhere, but what about the other things? Do they matter at all?
Edit: after the backup I now have a ton of tars, a recovery.img, and a boot.img. I extracted all of the tars, now do I just put all of the folders from the tars in a folder with the imgs and that's my base rom?
tuxboy said:
You can easily take a backup of your current ROM. Try booting into recovery and making your own custom recovery (ClockWordMod).
Click to expand...
Click to collapse
Okay, I've come pretty far and I've made several flashable zips and fixed many errors, but there's one thing I can't figure out - the updater script doesn't work, and I realized it's because I was using the one from the original port, and I need the one for my phone, which I can't get from the cwm recovery. I really need the whole META-INF folder. Where can I get that?
I tried for 1 week and i didnt find any official and stable rom for my samsung galaxy note 4 Sm 910h. I used resurrection remix unofficial and camara didnt worked there . Please any solution there help me