Database Develop

[WIP] MIUI Port -HELP NEEDED-

(Originaly Posted by popdog123)
This is a work i continue as popdog123 is very busy, so i think we shall do our best and let him work on his work, or whatever hes doing,
See The 2 Reserved, comments to get latest info!
Hello!
Ok so this is an attempt to port MIUI to LGP500. We are trying this because porting on the Galaxy 3 (LDPI armv6) was a success and i'm sure it will work on our device too.
This is what we're using so far: MIUI for Milestone, Desire & Overflow ROM
So far this has been done:
ADB now working
Merged framework.jar from base rom with MIUI one
Replaced all apks with miui except LatinIME.apk which seems to give an error on boot
Use libs, bin and xbin from base rom
Merged permissions
[Update 9.07.2011 - 17:48 GMT+3 DST]
Now using framework from CM7
Libs, and bins from CM7
Boot.img still from Overflow (CM7 Boot.img stops adb on boot after a while - so using Overflow for developing for now)
Replaced many smali files in framework but errors keep popping up - I think framework is pretty screwed up now and must be redone (again)
No more nasty error on boot (with stack dump and stuff...)
No need for logcat now because errors come from framework
[Update 11.07.2011 - 15:32 GMT+3 DST]
MIUI boots up and we have graphics BUT
It only boots up to some error dialogs that say some processes force closed with "Close" and "Report to MIUI"
Gapps, Provision, and StatusBar force close so they need work
Removed ContactsProvider.apk and CalendarProvider.apk
[Update 14.07.2011 - 10:58 GMT+3 DST]
Fixed framework.jar - no more errors seem to come from it
New zip not made on mac so no low memory errors
New problem that might fix the apps: All apps look for their classes.dex in /cache/dalvik-cache but only system classes are there. The app classes are created in /data/cache/dalvik-cache
All apps are back because the errors don't come from them
[Update 28.07.2011 - 18:53 GMT+3 DST]
Added dalvik-cache to /cache script
New zip with init.d script and updated framework
Need to fix dead code in framework
Need new kernel
Need MDPI apks
Need libs that don't make the apks crash
Latest flashable zip:
http://www.multiupload.com/VNM8QTDBZ3 [Updated 28.07.2011] Thank you 4silvertooth
10/14/2011
Replaced all Apk's (Now using latest MIUI 1.10.07 (STABLE)
Replaceed Android Policy (With Milestone's)
Replaced Services (With Milestone's)
still boots up, only FC was keyboard
(DOES NOT BOOT! DON'T FLASH IF YOU DON'T KNOW WHAT YOU'RE DOING!) Sorry... i had to put this in big red letters because apparently people didn't see it well...
If you would like to help go ahead. Download the rom or make your own one if you don't like our development and give input. But most of all don't try to bring us down with "this can't be done" stuff. It can be done and it was done for another armv6 device. We need to get apps and framework to work and rom to boot. Libs and bins will come after...
This being said i would like to thank these people for their work so far and for making me get off my ass and do something useful:
4silvertooth
jazux
DJoptimus-One
Also i would like to thank overflow for his rom. It's the base for our miui so far.

!
Special Thanks to!
Popdog123
For starting the port and to get it to even boot,
Thanks To!
4silvertooth (teaching me on how to)
jazux (telling me what to do)
DJoptimus-One (yeah he made stuffs also as i dont know)
For helping to get this port to work,

TO DO:
See the difference in this files:
android.policy.jar
services.jar
framework-res.apk
framework.jar
(as we only looked at framework.jar we)
we got no progress, but now we can do get it!
(Akash.gupta made the launcher work on galaxy 3, and on the port of MIUI)
Nothing is impossible we need to see what we are missing
and try to edit and recompile and test on our phone,

Whats the status so far ? I mean actually where have we reached ? What things aren't working ?
Sent via LG Optimus-One Gingerbread

why a new thread when old thread by popdog already exist are u taking over the rom assembling from here on .
whatt progess can we expect from this.....as it has beeen long since no update in old thread

shhbz said:
why a new thread when old thread by popdog already exist are u taking over the rom assembling from here on .
whatt progess can we expect from this.....as it has beeen long since no update in old thread
Click to expand...
Click to collapse
we can in hope for sure that we may soon get launcher to work as i now know that we cant only look into framework.jar we must check services etc,

DJoptimus-One said:
Whats the status so far ? I mean actually where have we reached ? What things aren't working ?
Sent via LG Optimus-One Gingerbread
Click to expand...
Click to collapse
the thing is for now same as before, but as popdog123 is busy and so many want this i actually will settle down and look into what is not correct in our files as in framework.jar , launcher, services.jar and framework-res.

SWEATTAIMI said:
the thing is for now same as before, but as popdog123 is busy and so many want this i actually will settle down and look into what is not correct in our files as in framework.jar , launcher, services.jar and framework-res.
Click to expand...
Click to collapse
Cool! All the best then and if you need any help. PM me or any other member of Team ENVY
We are always there to help
Sent via LG Optimus-One Gingerbread

DJoptimus-One said:
Cool! All the best then and if you need any help. PM me or any other member of Team ENVY
We are always there to help
Sent via LG Optimus-One Gingerbread
Click to expand...
Click to collapse
thing is for now we need to see what we are missing in our launcher and framework files

im so tired of you sweattaimiasdads.... ¬¬ always creating spam threads!

sewa2k said:
im so tired of you sweattaimiasdads.... ¬¬ always creating spam threads!
Click to expand...
Click to collapse
theres no spam thread, serious its you whos spamming delete the comment or i get mod to delete it for you!

Is this actually coming along now or is it still stumped??

scruffy3666 said:
Is this actually coming along now or is it still stumped??
Click to expand...
Click to collapse
i will see if i can get it to not fc as we have not all working parts, also the settings.apk seems damaged when using apktool it gives me alot of errors, so i think the settings is damaged

SWEATTAIMI said:
theres no spam thread, serious its you whos spamming delete the comment or i get mod to delete it for you!
Click to expand...
Click to collapse
Im sorry, but with your non-working roms u r the one whos spamming the entire dev section of P500.
First you start to "porting" ROMS to our P500, then, when u fail, start a new thread involving a "supercrazyamazing rom with extra-cheese", and only was a themed rom, but hey, no rom, because u cant figure it to enable sd-mount and show us screenshot of your fail (sorry, rom). Then u take others ppl work (like dr.notors) and continues as ur work? sorry m8 but im not spamming either threatening u with the mods. I dont even know why ur threads are still open.

sewa2k said:
Im sorry, but with your non-working roms u r the one whos spamming the entire dev section of P500.
First you start to "porting" ROMS to our P500, then, when u fail, start a new thread involving a "supercrazyamazing rom with extra-cheese", and only was a themed rom, but hey, no rom, because u cant figure it to enable sd-mount and show us screenshot of your fail (sorry, rom). Then u take others ppl work (like dr.notors) and continues as ur work? sorry m8 but im not spamming either threatening u with the mods. I dont even know why ur threads are still open.
Click to expand...
Click to collapse
again thats not spam, and i quited the rom and i do not have time,
The ihero is partly working, and SD-Card mounted,
Doktor notor's rom is not stolen i said i do a topic for it, as people may not go to his forum,
Please do read before posting man And why some threads is still open and not closed or deleted is because I or anyoneelse exept mod can close it (or administrator's) so i have tried close some topics with no luck, so what you can do is ask mod to do that for me ?

Well it would be great if you work on a single port and make it a complete success rom.
As dj said team envy is all there to help you out but we need a fully working rom as all the thread remains incomplete.
Well lets port miui :d

shhbz said:
Well it would be great if you work on a single port and make it a complete success rom.
As dj said team envy is all there to help you out but we need a fully working rom as all the thread remains incomplete.
Well lets port miui :d
Click to expand...
Click to collapse
yeah i thought that to, after some researches and questions i noticed that we only worked on framework.jar but we forgot 2 other files aswell

A quick tip from my side :- consider andy for the launcher. Remember his rom that was removed RC4.1 or something. He has always used a launcher actually and fully modified by HIM, and also with his upcoming legendary rom, he is doing the same with the launcher. All around the devs in O1 section, andy is the best in this field. You should ask him
I am 100% sure he will help and will take out some time for you.
JUST ONE RULE SHOULD BE FOLLOWED WHILE THIS :- BE PATIENT

DJoptimus-One said:
A quick tip from my side :- consider andy for the launcher. Remember his rom that was removed RC4.1 or something. He has always used a launcher actually and fully modified by HIM, and also with his upcoming legendary rom, he is doing the same with the launcher. All around the devs in O1 section, andy is the best in this field. You should ask him
I am 100% sure he will help and will take out some time for you.
JUST ONE RULE SHOULD BE FOLLOWED WHILE THIS :- BE PATIENT
Click to expand...
Click to collapse
your 100 thanks clicked.

ANDY:
as i see in the logcat, it seems that there are mixed libraries from miui and LG proprietary libs.
this cant work, because many apps are crashing at boot time because of missing functions for layout.
at first, remove the fu** LG drmserver - no one but LG need this.
second, try the surfaceflinger, surfaceflinger_client, libpixelflinger and liblayout from another rom,
these from LG rom cant work here - miui has patched many libraries, so these installed
cant work properly.
Click to expand...
Click to collapse
hmm we have missed something

[DEV][7/17][FIXES + FASTER] Jellybean - Collab (less broken stuff)

It's important for everyone to know that since this is a development thread, most, if not all conversation should be dedicated to helping us boot the ROM. All questions related to and including "will our device be able to handle Jellybean?" should be moved to the following thread: http://forum.xda-developers.com/showthread.php?t=1736089
Our biggest problem so far: There are incompatibilities with Jellybean and the Adreno drivers, which our phone needs to function. We can't just remove the Adreno drivers and boot the ROM (I tested this, by removing them from our latest CM9 nightly, which wouldn't boot as a result. I also removed the Adreno drivers and used the Jellybean ramdisk, framework, libs, and bin files but still no boot.).
PureMotive's port
I booted my source-built Jellybean.
Status: ALPHA
Working
Root
ADB
3G
WiFi
Calls (outgoing and incoming)
Signal
UI
Soft keys + lights
RIL
GPS
Brightness settings
Sync
SMS
MMS
Gmail
Gtalk
Twitter
Facebook
Audio
Downloads
Native screenshot (should work now)
Google Now
Untested
Video
Bluetooth
Camera
Broken
Butter
Browser (default)
HWA
Click to expand...
Click to collapse
Albinoman's port
Check his thread located here
Click to expand...
Click to collapse
PORTING FILES:
Code:
Jellybean SDK: [URL]http://d-h.st/EUH[/URL]
Jellybean Ramdisk: [URL]http://d-h.st/XhF[/URL]
Boot.img used in Tiny's port: [URL]http://d-h.st/a0C[/URL]
Vicious Jellybean (VZW GNex port): [URL="http://rootzwiki.com/topic/28486-rom-vicious-toro-jellybean-v3-100-functional-franco-kernel-beats-audio-mods-optimized-link-in-op-for-stock-kernel-added-112am-06302012/"]Vicious Jellybean[/URL]

On vacation. When I get back next week I'll check it out
Sent from my unrootable DROID2

where the hell is the ramdisk

Just wanted to mention my scan of the ramdisk the other night didn't lead to anything conclusive. I checked real quick yesterday I think but didn't really have time to look in depth. I didn't see a problem with the way the system mounted so something else is causing it. I'm trying to port it right now. We'll see what happens.

Maybe I should give it a try.

How about paste bin a logcat?

Here is my current logcat
http://paste.ubuntu.com/1074131/
Sent from my Droid Incredible using xda premium

Shano56 said:
where the hell is the ramdisk
Click to expand...
Click to collapse
Posted in the OP.
PonsAsinorem said:
How about paste bin a logcat?
Click to expand...
Click to collapse
We cannot get a logcat with the Jellybean ramdisk, even with these edits to default.prop:
Code:
persist.sys.usb.config=mass_storage,adb
persist.service.adb.enable=1
persist.sys.strictmode.disable=true
persist.service.adb.root=1
ro.secure=0
ro.allow.mock_location=1
ro.debuggable=1
service.adb.root=1
The error that follows is this:
Code:
'system/bin/sh' failed no such file or directory
Adding a "sh" file to /bin results in other errors (don't have them right now)
The only way a logcat will work is if we use the ramdisk from a CM9 ROM in addition to the CM9 libs.

PureMotive said:
Posted in the OP.
Click to expand...
Click to collapse
hehe now u post it. ty
edit: i thought you needed it extracted

PureMotive said:
Posted in the OP.
We cannot get a logcat with the Jellybean ramdisk, even with these edits to default.prop:
Code:
persist.sys.usb.config=mass_storage,adb
persist.service.adb.enable=1
persist.sys.strictmode.disable=true
persist.service.adb.root=1
ro.secure=0
ro.allow.mock_location=1
ro.debuggable=1
service.adb.root=1
The error that follows is this:
Code:
'system/bin/sh' failed no such file or directory
Adding a "sh" file to /bin results in other errors (don't have them right now)
The only way a logcat will work is if we use the ramdisk from a CM9 ROM in addition to the CM9 libs.
Click to expand...
Click to collapse
I got a port booting with your jellybean ramdisk. It won't go far but I'm about to provide a logcat after testing some changes. Toolbox and busybox work. I ported from the gnex. No boot screen but it does start to load files. Maybe you guys can figure it out from here. I'll upload it and my logcat after I test my zip.
Logcat linked below:
http://paste.ubuntu.com/1075642/
Initial Port Below:
http://d-h.st/shx

Upload!!!! Lol
Sent from my Droid Incredible using xda premium

tiny4579 said:
I got a port booting with your jellybean ramdisk. It won't go far but I'm about to provide a logcat after testing some changes. Toolbox and busybox work. I ported from the gnex. No boot screen but it does start to load files. Maybe you guys can figure it out from here. I'll upload it and my logcat after I test my zip.
Logcat linked below:
http://paste.ubuntu.com/1075642/
zip file coming next.
Click to expand...
Click to collapse
Did you use the ramdisk from the OP or the boot.img I sent you? I got it to the point where it would load the framework .jar files, but haven't encountered what you did in your logcat so I'd consider it progress lol. Seems to be an issue with EGL...
EDIT: Nevermind lol

The error that follows is this:
Code:
'system/bin/sh' failed no such file or directory
Adding a "sh" file to /bin results in other errors (don't have them right now)
Sounds to me like you are missing /bin/mksh either in ROM or in symlink in updater
Sent from my PG06100 using xda premium

Just wanted to first of all say thanks for this - it's awesome that this is even being worked on. We have such an awesome dev community. Secondly, just wanted to offer my support in any way possible. I don't have a lot of experience with porting Android, but I do have pretty good Linux system knowledge and a willingness to experiment. Downloading tiny's build now, going to mess around with some system files and see what happens. Thanks again guys!

Cm is going to working on cm10.
http://briefmobile.com/cyanogenmod-cm10-coming-with-jelly-bean-source-code-release
Sent from my ADR6300 using xda app-developers app

tiny4579 said:
I got a port booting with your jellybean ramdisk. It won't go far but I'm about to provide a logcat after testing some changes. Toolbox and busybox work. I ported from the gnex. No boot screen but it does start to load files. Maybe you guys can figure it out from here. I'll upload it and my logcat after I test my zip.
Logcat linked below:
http://paste.ubuntu.com/1075642/
Initial Port Below:
http://d-h.st/shx
Click to expand...
Click to collapse
Hey tiny4579 could you post what you changed/added in your build?

Albinoman said:
Hey tiny4579 could you post what you changed/added in your build?
Click to expand...
Click to collapse
I don't remember quite what I did and I'm not in a position to test but what if you take evervolv as a base and replace the app and framework folders with the ones from my port and the boot.img with the one from the port. It probably won't work by a long shot but at least it's worth a try.
Sent from my Galaxy Nexus using Tapatalk 2

I see progress! I will download your port right now and see what I can help you with.

tiny4579 said:
I don't remember quite what I did and I'm not in a position to test but what if you take evervolv as a base and replace the app and framework folders with the ones from my port and the boot.img with the one from the port. It probably won't work by a long shot but at least it's worth a try.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll try that later today. What version of evervolv are you using?
Sent from my Droid Incredible using xda premium

Albinoman said:
I'll try that later today. What version of evervolv are you using?
Sent from my Droid Incredible using xda premium
Click to expand...
Click to collapse
I was testing with 2.2.0a1.
Sent from my Galaxy Nexus using Tapatalk 2

[ROM] [CM9] [2012.11.11] De-Sensed Cyanogenmod 9 for HTC Vivid

Fully working Cyanogenmod 9 for the HTC Vivid calling, sms, data work.
And before you ask, yes its based on some of the HTC Frameworks, but i dont think anyone cares that much lol. When certain issues are fixed, i will pull out the htc stuff..
Issues:
-Apps randomly crash when downloading from google play.
-Certain options in settings cause device to crash.
-data randomly disconnects
-sometimes signal bars are inaccurate
LINK:
v0.1bhttp://q.gs/2Yy7E (dead zip)
v0.2 http://j.gs/1fJM (fixed zip but added problems
Sent from my HTC PH39100 using xda app-developers app
"Thanks/credits:
-Sensation CM9 devs for the base of this rom
-My mom for making me cookies this morning
-MG2195 for telling me to make this list
-Big thanks to theslam08 for fixing the ZIP
-Anyone else who I have forgotten

wow, pretty exciting news man!
cant wait for the link to test it...

Dude link!
Sent from my De-Sensed HTC Vivid using xda premium

What great timing... WildChild just banned me from his forum
Sent from my HTC PH39100 using Tapatalk 2

The skeptic in me wonders why it's based on 4.0.3...

altanimi said:
The skeptic in me wonders why it's based on 4.0.3...
Click to expand...
Click to collapse
its 4.0.4 i believe i screwed up some of the build.prop last night and thats what came out lol
and lmao @rignfool i hate that he did to me for "spamming"

Nice work...personally not a fan of HTC based aosp...as to me its not real aosp....but as you stated most people won't mind
Sent from my SGH-I997 using Tapatalk 2

I can't believe that I'm going to ask such a noob question, but what is the advantage of this build over wajee's de-sensed ROM?
Sent from my Nexus 7 using xda app-developers app

I hate to be a jerk but...
Link link link
Sent from my HTC PH39100 using Tapatalk 2

gotzaDroid said:
I can't believe that I'm going to ask such a noob question, but what is the advantage of this build over wajee's de-sensed ROM?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
cyanogenmod is based of aosp (basically what descended is) but with added features and tweaks...including easy theming, and much more customization abilities
rignfool said:
I hate to be a jerk but...
Link link link
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
If you look at the op he edited it saying 17 hours remaining....
Sent from my SGH-I997 using Tapatalk 2

mg2195 said:
Nice work...personally not a fan of HTC based aosp...as to me its not real aosp....but as you stated most people won't mind
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
haha thanks man.. same here but its a usable rom so hey, who cares lol

Ok everyone, having some trouble with the zip not flashing, will upload now because i dont have time to fix it now, have a soccer game, if anyone can fix it for me and send it back so i can upload it again thanks.

XxSHaDoWxSLaYeRxX said:
Ok everyone, having some trouble with the zip not flashing, will upload now because i dont have time to fix it now, have a soccer game, if anyone can fix it for me and send it back so i can upload it again thanks.
Click to expand...
Click to collapse
Any weird reason why half the app files are com.android.xyz.apk, com.google.android.xyz.apk and com.htc.xyz.apk?
The updater script appears with no problems though its a universal script for a few phones so will keep looking.
EDIT: Seems was something wrong with the first few lines of the script (using recovery.log). Removed those, did some other tweaking to it and now its installing. Will report back how it goes.
UPDATE: Well it boots, for some reason the bootlogo goes white after a few seconds of seeing the CM9 logo. Though it is booting. Anyway, will play around with it, seems nice and fast so far...will report
UPDATE2: Ok, its nice, but it is very buggy (OP is on point). If you are on virtuous, stay. Not much of the CM works, many settings crash (settings>display even crashes). I cant really stay on this to test more as I need a semi-working phone. But if the bugs could be fixed it would be a nice ROM. BTW it is only 4.0.3, same as others.

Thanks man and im not rly sure i think it screwed itself up when uploading to dropbox, il check when i get home
Also, make sure to install kernel from compuyer even if s-off had some problems with that
Sent from my HTC PH39100 using xda app-developers app

theslam08 said:
Any weird reason why half the app files are com.android.xyz.apk, com.google.android.xyz.apk and com.htc.xyz.apk?
The updater script appears with no problems though its a universal script for a few phones so will keep looking.
EDIT: Seems was something wrong with the first few lines of the script (using recovery.log). Removed those, did some other tweaking to it and now its installing. Will report back how it goes.
UPDATE: Well it boots, for some reason the bootlogo goes white after a few seconds of seeing the CM9 logo. Though it is booting. Anyway, will play around with it, seems nice and fast so far...will report
UPDATE2: Ok, its nice, but it is very buggy (OP is on point). If you are on virtuous, stay. Not much of the CM works, many settings crash (settings>display even crashes). I cant really stay on this to test more as I need a semi-working phone. But if the bugs could be fixed it would be a nice ROM. BTW it is only 4.0.4, same as others.
Click to expand...
Click to collapse
hey man could you upload the update-script. and thats wierd it works for me other than thememanager and themechooser crashing every 20 min lol
EDIT: nvm i could have sworn it was working last night..

XxSHaDoWxSLaYeRxX said:
hey man could you upload the update-script. and thats wierd it works for me other than thememanager and themechooser crashing every 20 min lol
EDIT: nvm i could have sworn it was working last night..
Click to expand...
Click to collapse
I cant actually upload mine because I changed alot, I reworked the folders so the holiday folder for the 'device' was just already in the system folder, where it ends up going anyways. Then I just left the simple extract /system line, so it does that. Also removed all the sdcard folder as I dont use any of those files anyway (except a few which I could download from GP if I needed it (ie. gmail)). So removed those lines and such. Also changed the boot line/folder so its on the main dir of the ROM, then using this line:
Code:
package_extract_file("boot.img", "/dev/block/mmcblk0p22");
instead I think makes things easier. I also changed the updater binary with another working rom.
Anyway, point is, not exactly where in all that it fixed it lol. But, 1 certain thing I can say is no matter what I did it said Status 6 on the zip install error. Doing report logs or something similar, go to the SD card and you will have a recovery.log file, open it and go to the end, it should say something like
Code:
line 1 col 14: syntax error, unexpected BAD
1 parse errors
E:Error in /sdcard/cm9-holiday-20121111.zip
(Status 6)
which is this:
Code:
ui_print("");
Which...is fine I thought, but idk. I removed down to line 14, removing the device lines too as I removed the device named folders, starting with the ui print formatting. Needless to say, it installed from there. So, just try removing that top part of your script and re-sign try again. Also, try the recovery.log process, that will point more to your problem.

theslam08 said:
I cant actually upload mine because I changed alot, I reworked the folders so the holiday folder for the 'device' was just already in the system folder, where it ends up going anyways. Then I just left the simple extract /system line, so it does that. Also removed all the sdcard folder as I dont use any of those files anyway (except a few which I could download from GP if I needed it (ie. gmail)). So removed those lines and such. Also changed the boot line/folder so its on the main dir of the ROM, then using this line:
Code:
package_extract_file("boot.img", "/dev/block/mmcblk0p22");
instead I think makes things easier. I also changed the updater binary with another working rom.
Anyway, point is, not exactly where in all that it fixed it lol. But, 1 certain thing I can say is no matter what I did it said Status 6 on the zip install error. Doing report logs or something similar, go to the SD card and you will have a recovery.log file, open it and go to the end, it should say something like
Code:
line 1 col 14: syntax error, unexpected BAD
1 parse errors
E:Error in /sdcard/cm9-holiday-20121111.zip
(Status 6)
which is this:
Code:
ui_print("");
Which...is fine I thought, but idk. I removed down to line 14, removing the device lines too as I removed the device named folders, starting with the ui print formatting. Needless to say, it installed from there. So, just try removing that top part of your script and re-sign try again. Also, try the recovery.log process, that will point more to your problem.
Click to expand...
Click to collapse
i checked it and changed something and instead of saying col 10 or something, it said col 17 >.< so im gonna go see if i can fix it again now.. thanks man

Wait...sounds like you included gapps (gmail was referenced above)
Be careful, there is a reason cyanigenmod doesn't include gapps be default
A while ago cyanogenmod used to include gapps by default until basically one day they got a nice letter from Google telling them they can not include there apps and if they did they would be sued. So since then gapps have been kept separate for legal issues...now the chances of you getting sued are unlikely as this is unofficial and not that big of a phone plus its not like your some huge software team...but you never know...just a warning keep em if you want (many do and to this day I don't think anyone has actually faced legal charges) but I always say better safe then sorry...
Sent from my SGH-I997 using Tapatalk 2

mg2195 said:
Wait...sounds like you included gapps (gmail was referenced above)
Be careful, there is a reason cyanigenmod doesn't include gapps be default
A while ago cyanogenmod used to include gapps by default until basically one day they got a nice letter from Google telling them they can not include there apps and if they did they would be sued. So since then gapps have been kept separate for legal issues...now the chances of you getting sued are unlikely as this is unofficial and not that big of a phone plus its not like your some huge software team...but you never know...just a warning keep em if you want (many do and to this day I don't think anyone has actually faced legal charges) but I always say better safe then sorry...
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
thanks man.. il pull 'em out when i get back to my computer..

wait is this just de-sensed with cm9 apks?

[DEV][WIP]Incredible Sense 3.6[No Boot][Apr.13.2013]

Here is my port thus far:
X Disclaimor - Rom does not boot meaning this is not working yet X
I think since sense 4 was obtainable I'd like to think Sense 3.6 is too.
Now, i'd like to ask for a little help if anyone is available.
Plus, I know developers because I am one; we have an insatiable palette for a good project.
I've discovered two things that have made me feel like i'm stuck:
4/12/2013
1) I am not sure what else I can remove from the system dir to decrease the size to what is needed ~ 272524902.4 bytes (259.9Mb)
The Roms system dir is ~274083573.9bytes (261.4Mb); I basically need to know what else I can get rid of that equal up to 1558671.5 bytes (1.5Mb)
Here's the catch- I already took out the weather from media and apps and have symlinked them from the data partition.
2) I am not sure if I have correctly made the kernel.
I have a boot.img from the sense 3.6 rom i used to port. And I added the bootclasspath from the base kernel.
I also have renamed the proper files that needed to be renamed with inc.
Update: 4/13/2013
I've shrunk the system/usr dir down and now the port is under the size limit.
I have also tinkered with the boot.img more. Can someone check it to make sure that I have done is okay..
`Link in my sig:

First thing check how we did it before using symlinks to make some of the files physically on data but linked to system.
Sent from my Galaxy Nexus using Tapatalk 2

tiny4579 said:
First thing check how we did it before using symlinks to make some of the files physically on data but linked to system.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So far I've symlinked system/media/weather to data/system.weather and the system/app dir to data/system.app.
This is what i'm using:
symlink("/data/system.app", "/system/app");
set_perm_recursive(0, 0, 0755, 0644, "/data/system.app");
symlink("/data/system.weather", "/system/media/weather");
set_perm_recursive(0, 0, 0755, 0644, "/data/system.weather");​
Do you think i could do the same with the system/vendor dir?
Edit: Don't need to worry now that the current port's system partition,which is now uploading, will be under the size limit.

*Bumpdated*
v1_1 Upload

Glad to see a Sense ROM getting some love.
Sent from my Infected HTC Incredible

We need to see how PureMotive got it booting on Sense 4. My brain's rusty on that project as it died a while ago and I am not sure how he got it to boot. I also need dedication to work on Sense after the superiority of AOSP on an aging device let alone ICS Sense. I don't know if I will have time to dedicate now that I'm working more on the Galaxy Nexus and a CM 10.1 ROM.

ChemicalSymphony said:
Glad to see a Sense ROM getting some love.
Sent from my Infected HTC Incredible
Click to expand...
Click to collapse
Yeah. I really wanna see this work lol. It's funny, I even dreamed I saw the Sense 3.6 taskbar on my Inc lol.
tiny4579 said:
We need to see how PureMotive got it booting on Sense 4. My brain's rusty on that project as it died a while ago and I am not sure how he got it to boot. I also need dedication to work on Sense after the superiority of AOSP on an aging device let alone ICS Sense. I don't know if I will have time to dedicate now that I'm working more on the Galaxy Nexus and a CM 10.1 ROM.
Click to expand...
Click to collapse
Yeah. Exactly. My brain is rusty too. I probably should try to find that Rom we worked on and see what the kernel looks like.
But don't worry about that, I think ppl like seeing devs even conversing together lol.

Tribulattifather said:
Yeah. I really wanna see this work lol. It's funny, I even dreamed I saw the Sense 3.6 taskbar on my Inc lol.
Yeah. Exactly. My brain is rusty too. I probably should try to find that Rom we worked on and see what the kernel looks like.
But don't worry about that, I think ppl like seeing devs even conversing together lol.
Click to expand...
Click to collapse
This is just a thought but couldent you for now pull the puremotive boot.img until you can build a patched kernel that you can push to the zip

zachf714 said:
This is just a thought but couldent you for now pull the puremotive boot.img until you can build a patched kernel that you can push to the zip
Click to expand...
Click to collapse
That's not enough on its own. Need to swap some files with those from an aosp ics build for the Inc.
Sent from my Galaxy Nexus using Tapatalk 2

tiny4579 said:
That's not enough on its own. Need to swap some files with those from an aosp ics build for the Inc.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll find a good stable ICS build then
Sent from my Nexus 7 using Tapatalk HD

zachf714 said:
I'll find a good stable ICS build then
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
How about the latest evervolv ICS release. That's what pure pulled from I believe.

@zachf714:
I will look also. If I find any, i'll upload them to the working folder i created for the project.
And if you guys find any, link me here and i'll download and do the same thing.
@tiny4579:
On the Luxe Rom we worked.. I don't have any of the files anymore. Do you happen to have a rom.zip of the project?
@project Community:
I've uploaded the Rom I used to port with to the dev host - droid in working folder.
I'm about to upload the other Rom I used.
Both the base and port rom I used to make the WIP are uploaded now.

Cm9 http://goo.im/devs/invisiblek/dinc/.../dinc-CM9-invisiblek-KANG-09-03-2012-1608.zip
This was actually the most stable ICS ROM I ran
Sent from my Nexus 7 using Tapatalk HD

I at least got a splash screen loop by flashing the boot.img from the cm9 rom
And man do I LOVE GITHUB https://github.com/PureMotive/sense36-ics-inc Those are the files Pure had put on Github

zachf714 said:
I at least got a splash screen loop by flashing the boot.img from the cm9 rom
And man do I LOVE GITHUB https://github.com/PureMotive/sense36-ics-inc Those are the files Pure had put on Github
Click to expand...
Click to collapse
That was an initial failed attempt. I think I worked on this with pure. Was it a fork?
Sent from my Galaxy Nexus using Tapatalk 2

tiny4579 said:
That was an initial failed attempt. I think I worked on this with pure. Was it a fork?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Not until I just forked it and yeah you did

Damn. Wish I wasn't in bed already.
I'd compile pures git and see if his kernel does anything with the WIP.
My kid gets on the bus at 7:50a (est) and will Dev a bit before I get going for the day.
But if someone tries before then let us know the outcome.

I'm transferring over two versions of the WIP now.
One with the boot.img from pure's git injected into it.
And another that is redesigned to look like how pure had it. Also, I merged my bin, lib and xbin.
Also using the boot.img from pure.
Testing in a minute or so and i'll report back with the outcome.
(Off topic ~ Today's my 4 year anniversary being at xda )
Edit: Yeah, they both didn't work. I'm uploading v0_3 now so you guys can take a look at what I did.

Tribulattifather said:
I'm transferring over two versions of the WIP now.
One with the boot.img from pure's git injected into it.
And another that is redesigned to look like how pure had it. Also, I merged my bin, lib and xbin.
Also using the boot.img from pure.
Testing in a minute or so and i'll report back with the outcome.
(Off topic ~ Today's my 4 year anniversary being at xda )
Edit: Yeah, they both didn't work. I'm uploading v0_3 now so you guys can take a look at what I did.
Click to expand...
Click to collapse
I just thought about this but maybe the updater script is bad
Sent from my ADR6300 using Tapatalk 2

zachf714 said:
I just thought about this but maybe the updater script is bad
Sent from my ADR6300 using Tapatalk 2
Click to expand...
Click to collapse
That is exactly what I thought so took care of that hahaha.
Right now, imo, I'm thinking it's a lib problem from my recent logcat.
I'll hop on in a few minutes and take another logcat and upload it.
(I deleted the one I had because I hadn't realized that you all might want to take a look too)

[GUIDE]How to Port ROMS from same resolutions phones- Easy way

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