Related
(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
CM7.2 Pons
Goo.Im Download for Kangs
Dev-Host Mirror
(updated only on request)
MediaFire Mirror
(updated only on request)
Changelog
Gapps
Gapps Mirror
Merged Commits for Gingerbread
Open Commits for Gingerbread
CyanogenMod 7 for the HTC Incredible :: V7.1.0 (9 Oct 2011)
Credits/Thanks
All credit goes to Cyanogen and the rest of the CM team, and especially our HTC Incredible maintainers, as listed by the CyanogenMod site: jistone (aka CUViper/This Guy), slayher, and of course, koush, as well as the authors of the respective open commits.
Why a new the thread? The build bot has retired (as far as CM7 nightlys are concerned), and the current thread at [ROM] CM7.2 Nightlies for the Droid Incredible was designed with the official nightlys in mind. It has since deviated from that original aim, and to keep it from going off topic any further, I have created this thread.
For some reason, I have received several requests to put a donation link in my profile. You can always donate to the CyanogenMod project, but if you feel you HAVE to donate to me, I've put a link in my profile, and all donations will go towards upgrading my computer, so I can stay on top of this for CM9.
Changelog
In case you missed it the first time.
Known Issues/Bugs
Per slayher: "Sometimes things are going to break, sometimes features are going to be removed, then added, then removed, then added back."
Just because it works in one build, doesn't mean it's going to work in the next.
TV-Out doesn't work on CM7 or any AOSP ROM
720P video recording
Theme Chooser causing WL widgets to disappear
FAQ
Q: What's the ETA on....about how long till...when can I expect....?
A: The only rule of CyanogenMod: You don't ask for ETAs.
Q: Now that the Ice Cream Sandwich SDK has dropped, we're getting a port, right?!
A: Take a look at this PSA by Keyan Mobil
Q: What's this CM7.2, Android 2.3.7 business?
A: The kangs are built towards CM7.2, which is Android 2.3.7.
Q: How do I install a CM7.2 kang, coming from non-CM7?
A: The safest (definitely not the only, but my preferred) way is
Download kang from link
Reboot into recovery.
Make a backup/nandroid (to be safe)
Format system and boot under mounts
Wipe Data/Factory reset
Install zip from SDCard
Flash kang.
Flash Gapps (if this is your first time flashing a kang/CM7
Reboot
Enjoy
If any of you have data that you must absolutely save, then and only then should you use Titanium backup (or other backup apps) to restore your data. Please be sure not to restore any data to /system using these apps, as this will mostly likely corrupt your ROM.
Q: How do I update/flash these kangs?
A: The safest (definitely not the only, but my personal) way is
Download kang from link
Reboot into recovery.
Make a backup/nandroid (to be safe)
Wipe Cache
Wipe Dalvik
Install zip from SDCard
Flash kang.
Reboot
Enjoy
Q: How about that 720P? I hear it's handy.
A: Per slayher, "720P recording will not be coming to CM7 at this time. We *MAY* see it later if we get an HTC GB leak, using an MSM device (aka not omap). But for now, if you HAVE to have 720P recording, stick with CM6. The issue is that GB uses stagefright, and the hack it took to get 720p in CM6 wont work with stagefright. (it was done in opencore.) This is why we cant get it. The current driver implementation we have to work with is just not capable. So there you go, you can stop wondering/asking/hoping."
Q: How about CWM3/5? I'm having a problem where....
A: Try deleting the current recovery first.
Q: How do I fix the space error that pops up when I try to install some apps?
A: Per slayher, "If you get a Space error trying to install apps, just try installing again. I have encountered this error also and it is not related to actual free space, (unless you have a cubic crap ton (crapton * crapton * crapton) of apps installed)."
Q: How do I disable the shutter sound?
A: Per mattyg151, "I used root explorer to rename /system/media/audio/ui/camera_click.ogg to camera_click!.ogg ... no more camera shutter sound."
There is also an option at Menu > Settings > CyanogenMod setting > Sound > Mute camera shutter
Q: How do I increase the WiFi scan time to save battery life?
A: Per karnovaran, "One way to reduce battery drain is to increase the WiFi scan interval. It's set to 45 seconds, meaning it will scan every 45 seconds. If you change it to something like 90, obviously it will scan less often and use less battery. To do this, you have to edit the build.prop file in /system. The easiest way is with Root Explorer. Go to /system, mount r/w, open the build.prop in text editor and locate "wifi.supplicant_scan_interval=45" Change that value to 90 or whatever you want. Save the file, mount back to r/o, and reboot."
Q: Those automatic brightness settings are confusing. Anyone know of a good setting/rough guide?
A: This thread looks useful. So does this post
Q: How does that brightness slider thingey-majib work?
A: Per byrong "For those of you trying to figure out the new brightness-adjust-via-statusbar feature, do the following:
1. Settings > CM Settings > Interface > Status Bar Tweaks > StatusBar brightness (I'm guessing you guys already figured this part out)
2. Here's the trick: place your finger on the status bar, but don't drag it down. It will still 'peek' out some, but now you'll want to slowly drag your finger to the left or right while keeping it on the status bar itself. If you drag left, the screen will get darker; right for bright."
Q: I can't send no fancy mms picture messages!
A: Change you APN settings manually, (a popular way is to use GoSMS).
MMSC: http://mms.vtext.com/servlets/mms
MMS proxy: leave empty
MMS port: 80
Any more I should add? Let me know.
Sweetness. Thanks, Pons!
Clean and organized.
Redid the changelog that I use to keep track of the open commits. Linked it to a public viewable google document so I only have to maintain one across different sites.
Let me just say it was painful copying and pasting the thread from Rootz to here. Even after I tidied it up for xda's forum, it still looks terrible to me, especially compared to Rootz. XDA needs to switch forum software.
Thanks for putting these together! Been wanting to go back to something AOSP; this is a great way to get into it.
You're the man! Thanks so much for setting this up and maintaining for us. Your kangs are dope! Just wanted to say thanks man!
Thanks man.
-My life is a shooting range, people never change-
Great idea devoted thread for the kangs. Honestly I did not know you were doing that and I was using #258 still. Who knows what small differences I'll never notice I am missing. Time to flash.
I had to upgrade to a nexus but now I can unleash my Dinc from Verizon and "phone" duties.
I hope this isn't a dumb question, but what are Commits, and what is the difference between merged commits and open commits?
I've been running one of the kangs for a few days now and I love it. I was just curious because I see the survey at the top of the page and a couple links about commits, but I don't know what they are and after just a quick search I haven't found anything.
BlankDEP said:
I hope this isn't a dumb question, but what are Commits, and what is the difference between merged commits and open commits?
I've been running one of the kangs for a few days now and I love it. I was just curious because I see the survey at the top of the page and a couple links about commits, but I don't know what they are and after just a quick search I haven't found anything.
Click to expand...
Click to collapse
CyanogenMod goes through a review process, where anyone can submit code. The code submitted is called a commit. If it passes scrutiny and works, it gets merged into the official CM repository. This approved commit is called a merged commit. All official nightlys (and RC's and stables when they get to that point) only have merged commits.
An open commit is a change to the code that is currently being reviewed and hasn't been approved to be included in the next CM...yet, or ever for that matter. Some open commits get merged eventually (either as they are, or after they've been updated a time or fifteen), other open commits get abandoned. Some users like the additional functionality of these open commits, at the potential cost of stability.
I've started releasing kangs two at a time. One completely stock with only merged commits (just like the official CM7 build bot would have done, may it rest in peace), and the next kang with the same amount of merged commits, plus some interesting looking open ones (most have been requested by users, other merely look like they won't make your phone explode).
And don't hesitate to ask questions, at least after a quick google search.
Pons do you know why we don't have TV out yet? We have kernel source now I thought.
PonsAsinorem said:
CyanogenMod goes through a review process, where anyone can submit code. The code submitted is called a commit. If it passes scrutiny and works, it gets merged into the official CM repository. This approved commit is called a merged commit. All official nightlys (and RC's and stables when they get to that point) only have merged commits.
An open commit is a change to the code that is currently being reviewed and hasn't been approved to be included in the next CM...yet, or ever for that matter. Some open commits get merged eventually (either as they are, or after they've been updated a time or fifteen), other open commits get abandoned. Some users like the additional functionality of these open commits, at the potential cost of stability.
I've started releasing kangs two at a time. One completely stock with only merged commits (just like the official CM7 build bot would have done, may it rest in peace), and the next kang with the same amount of merged commits, plus some interesting looking open ones (most have been requested by users, other merely look like they won't make your phone explode).
And don't hesitate to ask questions, at least after a quick google search.
Click to expand...
Click to collapse
Thank you so much for the response. It makes a lot more sense to me now. I might take a look at what some of those open commits do and test them out, I have not problem having to restore or flash a newer stabler one if needed.
BlankDEP said:
Thank you so much for the response. It makes a lot more sense to me now. I might take a look at what some of those open commits do and test them out, I have not problem having to restore or flash a newer stabler one if needed.
Click to expand...
Click to collapse
Good on ya mate! Take a chance and get cool features that may never be available
Sent from Tapatalk
Thanks, Pons. These KANGs brought me back to CM7 after like 9 months on MIUI builds. Just got tired of the instability and random problems with the new MIUI builds. These CM7 kangs are awesome. Great work!
Kitchen theming not sticking
Sorry if this is a dumb question, I haven't been on CM7 in a while, and hadn't tried using UOT for anything on it before.
I set up a new battery style and applied the zip. It themed over fine after booting up, but eventually it reverted to the stock CM7 battery after an hour or so.
Anyone have any suggestions on getting a new battery style to stick? Thanks.
miketwoms said:
Sorry if this is a dumb question, I haven't been on CM7 in a while, and hadn't tried using UOT for anything on it before.
I set up a new battery style and applied the zip. It themed over fine after booting up, but eventually it reverted to the stock CM7 battery after an hour or so.
Anyone have any suggestions on getting a new battery style to stick? Thanks.
Click to expand...
Click to collapse
You can another way but it may be a little more complicated? Not onto recovery, mount system, then adb pull the systemui.apk, decompile it with apk manager, swap out the png's for the battery with those from the SystemUI.apk, recompile the SystemUI.apk, then pull the png's from the recompiled apk with 7Zip and drop them into the original SystemUI.apk, and adb push it back to the phone.
EDIT: And although I haven't tried this next method, it may work? You could boot into recovery, mount the system, adb pull the SystemUI.apk, explore it with 7Zip, and simply drop the battery png's from the uot (which you are exploring the same way) into the folder the battery png's are located in within the SystemUI.apk and it will overwrite them (provided the files are named the same. They NEED to be named exactly the same). the adb push that systemUI.apk back to the phone. No decompiling or Recompiling done...
So yeah, not sure if that will work do to compression and stuff..
Sent from Tapatalk
thanks. I might give that 2nd option a try.
[CONTEST #5] CDMA Nexus: People's Choice Edition
Vote for The CM maintainer for the OG Incredible Josh Stone aka CUViper.
http://rootzwiki.com/user/25563-cuviper/
He's been great to us and the incredible community; let's try and return the favor.
New kang is up. Check the changelog, and/or download location.
This thread is intended for developers and others who can contribute to the project
If you think you can contribute, please do so
Standard disclaimer:
I am not responsible if anything happens to your device
Status:
Device specific build of Ubuntu's minimal cm10.1 build ready
Ready for flashing
Working:
Touch screen
ADB
Browser (Although no net access yet)
You can browse and get a feel of the entire OS, including the homescreen (unity desktop), multitasking (the cool new way to switch between apps), etc.
Since it is a preview, many apps are dummy apps.
Screenshots:
Check them out here
Video:
Here is a video of the fresh new OS in action on the O2x made by JordanRulz
Download links:
Ubuntu touch preview (raring ringtail)
Current build of Ubuntu-CM10.1 (old bootloader)
New bootloader build by delaya73:
cm-10.1-20130604-UNOFFICIAL-p990.zip
Older Ubuntu phone quantal image
older build 2 of Ubuntu-CM10.1 by delaya73
older build 1 of Ubuntu-CM10.1 by delaya73 for the new bootloader
TWRP latest version is recommended (CWM 6.x may work too)
Note:
The raring/quantal image is large, but thankfully gets installed on the data partition, thus saving our small system partition the burden
Source:
Ubuntu-cm10 source
Building instructions:
Building instructions are similar to building CM10 (refer Raum's guide) till repo sync (instead of official cm10 repo, use above source during repo init)
Dont forget to add device props in "local_manifests" (local_manifest.xml is deprecated). Add the following in local_manifests:
Code:
(Taken from Raum's guide, thanks to him)
After syncing the repo,
1. cd device/lge/p990, connect your device running cm10.1 with usb debugging on, and then ./extract-files.sh
2. In device/lge/p990/fstab.p990, remove "nosuid" from data partition
3. In kernel/lge/star/arch/arm/configs, in cyanogenmod_p990_defconfig, add the following:
Code:
CONFIG_SYSVIPC=y
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
CONFIG_DEVTMPFS=y
CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_FANOTIFY=y
CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y
CONFIG_FSNOTIFY=y
CONFIG_SWAP=y
# CONFIG_ANDROID_PARANOID_NETWORK is not set
4. Go to ubuntu folder inside your source folder and do
Code:
bzr branch lp:phablet-extras/libhybris hybris
bzr branch lp:platform-api platform-api
If you didnt have bzr, get it first using
Code:
sudo apt-get install bzr
Now you can build. This build would be for the old bootloader. For the new one, make these changes said by pengus77 here
Flashing instructions:
1. Make a full wipe (wipe data + format /system)
2. Flash the current build and raring/quantal image
Then flash this afterflash.zip
3. Reboot
Credits:
Ubuntu dev team (Canonical)
Ricardo and the rest of the CM team
delaya73 for the new bootloader build
pengus77 for bringing cm10 to the new bootloader
Adam77Root for helping find the missing components stopping it from booting
All other contributors
AW: [DEV][WIP] Porting Ubuntu Phone for LG Optimus 2x
You rock man!
Gesendet von meinem LGP990 mit CM10.
Good luck with your job, Buddy, and Congratulations for all your interest/performance for our machines!
Regards.:good:
Thnx, I downloading, after a try, I will post some feedback
R: [DEV][WIP] Porting Ubuntu Phone for LG Optimus 2x
Can i have some screenshot?
Sent from my LG-P990 using xda app-developers app
rugglez said:
"...If you think you can contribute, please do so ..."
Click to expand...
Click to collapse
I have not had time to install this ROM ... I have been testing other, but lack little longer to do so!
Once you have news post here the results.
Thank you all for the effort made
Thank you man you're doing a really good job
Very good job rugglez bro. cant wait for bootable version to test it on my self
Well, I tried to make some tests to see if he could complete the boot ... unfortunately without success after six or seven attempts.
Enough for today testing, hahahaha! ...
So finally your Repo synced! I've left Hope here! And yea, Rugglez Bhai, you are great! )
rugglez said:
This thread is intended for developers and others who can contribute to the project
If you think you can contribute, please do so
For now, this is only for the new bootloader. If the project is successful, it would be made available on the old one as well
Standard disclaimer:
I am not responsible if anything happens to your device
Status:
Device specific build of Ubuntu's minimal cm10.1 build ready
Ready for flashing
Does not complete the boot yet
Download links:
Current build of Ubuntu-CM10.1
Ubuntu kernel for O2x
Ubuntu phone quantal image
TWRP latest version is recommended (CWM 6.x may work too)
Instructions:
1. Make a full wipe (wipe data + format /system)
2. Flash the current build, Ubuntu_kernel and quantal image
3. Reboot
Note:
The quantal image is large, but thankfully gets installed on the data partition, thus saving our small system partition the burden
To do:
There is no "logcat" in Ubuntu (may be some other way to debug), so need another way to look at what is preventing the boot
Credits:
Ubuntu dev team (Canonical)
CM team
All other contributors
Click to expand...
Click to collapse
have u tried dmsg/kmsg?
how did u get a bootanimation on there ?, my nexus 7 with ubuntu phone os, dont have one, on the nexus 7 there is only a black screen for a seconds then it boots up
Re: [DEV][WIP] Porting Ubuntu Phone for LG Optimus 2x
Never got around to syncing myself, I'm a bit confused regarding the post, so is it usable?
Sent from my LG-P990 using xda app-developers app
JordanRulz said:
have u tried dmsg/kmsg?
Click to expand...
Click to collapse
Will try that today. Not sure if ill get time, but if you could also have a look, it would be great. Saw that you have some experience with this
FettleifIsMyUserName said:
how did u get a bootanimation on there ?, my nexus 7 with ubuntu phone os, dont have one, on the nexus 7 there is only a black screen for a seconds then it boots up
Click to expand...
Click to collapse
Boot animation comes from the Ubuntu-cm10.1 build and is the default cm10 boot animation. Since your tablet's Ubuntu image was released directly by canonical, they must have removed the cm10 boot animation before releasing it
Neefy said:
Never got around to syncing myself, I'm a bit confused regarding the post, so is it usable?
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
If you read the first post, it's written there that it does not complete the boot yet, still a WIP.
The reason I posted was that if more contributors join in, more expertise, more time, better debugging and much higher chance of project success
Jishnu Sur said:
So finally your Repo synced! I've left Hope here! And yea, Rugglez Bhai, you are great! )
Click to expand...
Click to collapse
Thanks
Come online later, I'll help you fix that issue. Install and keep team viewer ready
After watching some vids about this OS, it trully have a great potential. gonna watch this thread closely for progress
Re: [DEV][WIP] Porting Ubuntu Phone for LG Optimus 2x
rugglez said:
Thanks
Come online later, I'll help you fix that issue. Install and keep team viewer ready
Click to expand...
Click to collapse
Nice to know that the team is joining up and viewing to do great things
Great going guys
O2X with Magical ICS ROM and magnificent kernels from my buddies
rugglez said:
Will try that today. Not sure if ill get time, but if you could also have a look, it would be great. Saw that you have some experience with this
Boot animation comes from the Ubuntu-cm10.1 build and is the default cm10 boot animation. Since your tablet's Ubuntu image was released directly by canonical, they must have removed the cm10 boot animation before releasing it
If you read the first post, it's written there that it does not complete the boot yet, still a WIP.
The reason I posted was that if more contributors join in, more expertise, more time, better debugging and much higher chance of project success
Thanks
Come online later, I'll help you fix that issue. Install and keep team viewer ready
Click to expand...
Click to collapse
M always ready!!!!!!!!! =D
The Credits list looks too small.
Maybe you can add Ricardo Cerqueira (for ahem) and TonyP for porting TWRP.
jasjeev4 said:
The Credits list looks too small.
Maybe you can add Ricardo Cerqueira (for ahem) and TonyP for porting TWRP.
Click to expand...
Click to collapse
......and so on...!...
jasjeev4 said:
The Credits list looks too small.
Maybe you can add Ricardo Cerqueira (for ahem) and TonyP for porting TWRP.
Click to expand...
Click to collapse
Ricardo is always a name in every project of the O2x, and he is a part of the CM team, in case you didnt know
But thanks for the reminder, I explicitly specified his name too now, deserves so much credit for bringing CM10 to our device.
Tonyp is a great contributor and we are thankful for all his work. But this is a ROM, and TWRP is a recovery used to flash a ROM, they have non-overlapping work. What I mean is, this ROM doesnt use TWRP's work, rather it can be flashed in TWRP or CWM6.
By your logic, Koushik Datta (developer of CWM and one of the best android devs) should be included in every ROM's credits here. Also, creators of USB, personal computers, internet, world wide web, which are also tools used in the process of flashing it.
(No offense meant to any of the above, they are all revolutionary people whom I greatly respect)
My point is, if I am using someone's work in this project/ROM, thats the person whose name goes in credits, not the one who is creating the tools to install it.
It's better if the discussion doesnt go further about this off-topic thing, if you find that I have used anyone's work in this ROM and not given credits, please let me know, thanks
Let's try to make Ubuntu Phone OS boot on our phone. Thats the priority here. Didn't get much time today, got college this week too, will see if I get time to work on it soon
A. Why change RIL?
Hey, everyone.
As a user that's been using custom roms since our bootloader was unlocked, I'm aware that some of us have some issue with telephony & mobile data (in short, RIL) - occasionally IMEI wouldn't be read on boot, which would lead to device not being registred on network. Sometimes, the network would "die" in a way - you'd get an error when trying to dial a number, and when someone would call you, they'll hear the ringing tone while your cell phone would not ring at all.
The cause of the problem seems to be some lazy coding by official CM developers/maintainers for our device. This was picked up by a developer named kholk, so he did his best to recode it properly, however it was never included into official CM device tree for reasons unknown to me (more info about the issue can be found here: http://review.cyanogenmod.org/#/c/47980/).
Kholk did include his own custom RIL into his EPRJ roms, but the roms are kinda old and have iffy baseband (which seems to be kernel issue, as he's using his own, 3.4 kernel instead of CM's 3.1 kernel in other custom roms).
So, with the help of Adam77Root, I've learned a way on how to implement EPRJ RIL into other custom roms (since I still had RIL issue with default CM RIL in 4.3 roms even) - so far I've tested it with Vanir 4.3, Carbon 4.3, Carbon 4.3.1, and few 4.2.2 roms, and I havent had ANY issues I had in CM RIL.
So, this is a tutorial to show you how you can import EPRJ RIL to any custom rom you'd like, in case you have issues with cell connection.
-this should work on any kernel and any custom rom (4.2.2+)! Tested so far, as far as kernel goes, are iodak 8/8.5, WWJB8/8b, Optimus Prime several versions, Optimus Play! 2.53.
-KK roms tested are P.A. by @dcos which has eprj ril by default, official CM nightlies and several others
-some KK roms, for some reason, don't have x3ril.smali file in their telephony-common.jar. To implement EPRJ RIL in these roms, follow the tutorial up to point 5, and skip that one, since you don't have anything to delete. After point 13, you need to do one additional thing - you need to edit ROM's build.prop settings, look for this line: "#ro.telephony.ril_class=X3RIL", and delete "#" so this line would be included in build.prop. After that, you're ready to flash. Thanks goes to @gerciolisz for the tip on the build.prop settings.
-/As of 24.01.2014. i've added another zip file which contains x3ril.smali taken from P.A. port by dcos - i'd recommend using this one for 4.4.2 roms/
-as of 11.06.2014., I've added x3ril.smali (it's in omni-v1.rar) made by adam, which is based on omni's RIL but has eprj RIL recovery. if you're on 4.4.3 kitkat rom and have issues, i suggest you give this file a try first before others
B. What's needed?
First off, you'll need a few things:
- Android Multitool from http://forum.xda-developers.com/showthread.php?t=2326604, many thanks to @Flextrick
- Read the linked topic - it's the instruction on how to use it, and in case you encounter any errors, that's the place to search for solutions
- Attached is a RAR with two files in it, X3RIL_old.smali and X3RIL_new.smali. You need only one of those - but more info about them will be in the other steps.
- Custom ROM you want to edit
- Common sense
- WinRAR & JAVA
C. How to change RIL?
Steps:
1. First step is to open the .zip of your custom ROM you want to edit, and search for system/framework/telephony-common.jar
2. Extract it to AndroidMultitool/Files, and after extract is done, delete it from .zip
3. Open Android Multitool, under Decompiling select .jar, then select telephony-common.jar in AndroidMultitool/Files, click "decompile"
4. After you're done, check if there were any errors in the Log, in AndroidMultitool main window
5. Head over to AndroidMultitool/Decompiled_jar/telephony-common/com/android/internal/telephony and look for X3RIL.smali. This is CM's RIL implemented in custom roms, which we dont need anymore, so delete it
6. Now, you need to decide wether to use X3RIL_old.smali, which is RIL from EPRJ CM10.2 built on 20130813, or X3RIL_new.smali which is RIL from EPRJ CM10.2 built on 20131007. I'm using 20131007 atm, and it's working without issues
7. When you've decided, move it back into AndroidMultitool/Decompiled_jar/telephony-common/com/android/internal/telephony and rename it to X3RIL.smali
8. Back in AndroidMultitool, under Compilin, select jar, and for folder select AndroidMultitool/Decompiled_jar/telephony-common, press "compile", and check for errors in Log
9. Output should be classes.dex file under AndroidMultitool/Compiled_jar
10. Open telephony-common.jar in AndroidMultitool/Files with WinRar - you should see META-INF folder, with classes.dex file
11. Delete classes.dex file in WinRAR
12. Move classes.dex file from AndroidMultitool/Compiled_jar to telephony-common.jar opened in WinRAR
13. Paste telephony-common.jar into system/framework inside the custom rom .zip file
14. You now have modified ROM ready to flash on our device!
D. Thank You's
Thank you's go out to @kholk for his RIL programming, @dcos for first implementing EPRJ RIL into a rom (his P.A. unofficial port for our device) different than EPRJCM10.2, @Adam77Root for his tutorial that I basically beutified and made sure is easier to understand & his modification of x3ril.smali from omni, @gerciolisz for the tip about build.prop settings, @Flextrick for his Multitool with neat GUI to extract .jar files, and all the other devs of p880 making our device worth every dime I've spent on it.
Flying_Bear said:
Kholk did include his own custom RIL into his EPRJ roms, but the roms are kinda old and have iffy baseband (which seems to be kernel issue, as he's using his own, 3.4 kernel instead of CM's 3.1 kernel in other custom roms).
Click to expand...
Click to collapse
Dude, i think you missed out the clarification for the users on whether or not they need to use the EPRJ Kernel and if anykernel will still work or normal kernels will work etc. Because your bound to have the first person to ask a question will either be, "How do i declare java paths" and "Will 'kernel name here' work with it", this isnt me asking, more of an fyi post (Y)
I do apologize about it, but saves you the time and effort of answering the question every day
MOD EDIT: watch your language please.
penguin449 said:
Dude, i think you missed out the clarification for the users on whether or not they need to use the EPRJ Kernel and if anykernel will still work or normal kernels will work etc. Because your bound to have the first person to ask a question will either be, "How do i declare java paths" and "Will 'kernel name here' work with it", this isnt me asking, more of an fyi post (Y)
I do apologise about it, but saves you the time and effort of answering the question every day
Click to expand...
Click to collapse
np, thanks for the tip. i'll add in OP that it works with any kernel
MODERATOR EDIT: @penguin449 watch your language
I flashed Vanir nightly 171013 with Optimus Prime 2.70 kernel and telephony was completely disabled. I was not able to find or register to the mobile network. I tried modifying the RIL file as explained in this post; initially with the "new" file which didn't seem to solve the problem (still didn't get signal) but I didn't wait I immediately tried flashing the ROM with the "old" RIL instead. Initially there was no signal although I was able to find networks, but after a reboot the phone finally managed to connect to the mobile network.
I'm not sure whether it would've worked after a reboot with the "new" but I'm guessing if it's working with the "old" RIL I got nothing to worry about right?
Vanir is 4.3.1 while OP is for 4.3, i think thats your problem. Different RIL would not help in that case. Flash Anykernel version of OP, or find a version repacked with 4.3.1 ramdisk. Good luck!
Flying_Bear said:
Vanir is 4.3.1 while OP is for 4.3, i think thats your problem. Different RIL would not help in that case. Flash Anykernel version of OP, or find a version repacked with 4.3.1 ramdisk. Good luck!
Click to expand...
Click to collapse
As far as I understood, the 171013 version did not have the RamDisk issue so I figured the CM10.2 version of Optimus Prime kernel should've worked correctly?
So I get it from you that if I flash the original rom with the AnyKernel version of OP it should work fine? (no need for any RIL modifications?)
Yep, anykernel versions of all our kernels xcept iodaks should work on any android version without any modifications.
Is there a way to do this with Linux?
If not, how about uploading modified telephony-common.jar for CM ROMs?
I tried just replacing the whole telephony-common.jar file but I couldn't send or receive any messages. Everything else seemed to work though.
Sent from my LG-P880 using Tapatalk
MilkyJoePD said:
Is there a way to do this with Linux?
If not, how about uploading modified telephony-common.jar for CM ROMs?
I tried just replacing the whole telephony-common.jar file but I couldn't send or receive any messages. Everything else seemed to work though.
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
not sure really, since i havent worked on linux systems.
and i dont think telephony-common.jar is universal for all roms (i might be mistaken though), so there's no use to upload it. however, if you want, upload your original telephony-common.jar file here and i'll do my best to mod it for you!
Flying_Bear said:
not sure really, since i havent worked on linux systems.
and i dont think telephony-common.jar is universal for all roms (i might be mistaken though), so there's no use to upload it. however, if you want, upload your original telephony-common.jar file here and i'll do my best to mod it for you!
Click to expand...
Click to collapse
I meant it would be a good idea to have a place to download the modified files for specific ROMs.
Here's the (unmodified) file for Vanir.
https://app.box.com/s/embcq9kuemfdkdb1qw63
Thanks.
Sent from my Optimus 4X HD using Tapatalk
MilkyJoePD said:
I meant it would be a good idea to have a place to download the modified files for specific ROMs.
Here's the (unmodified) file for Vanir.
https://app.box.com/s/embcq9kuemfdkdb1qw63
Thanks.
Sent from my Optimus 4X HD using Tapatalk
Click to expand...
Click to collapse
well, we have way too much roms for me to download each one and replace the RIL ^^
anyway, here's your modified telephony-common ^^ enjoy!
Flying_Bear said:
well, we have way too much roms for me to download each one and replace the RIL ^^
anyway, here's your modified telephony-common ^^ enjoy!
Click to expand...
Click to collapse
I suppose there is a lot.
I'll test the Vanir one and report back.
If it works then there's a start. I can send messages so it works so far. The only thing keeping me from staying on a CM ROM is the random signal loss.
Sent from my Optimus 4X HD using Tapatalk
MilkyJoePD said:
I suppose there is a lot.
I'll test the Vanir one and report back.
If it works then there's a start. I can send messages so it works so far. The only thing keeping me from staying on a CM ROM is the random signal loss.
Sent from my Optimus 4X HD using Tapatalk
Click to expand...
Click to collapse
check it out, this should fix that issue completely. and report when you have time ^^
Flying_Bear said:
check it out, this should fix that issue completely. and report when you have time ^^
Click to expand...
Click to collapse
If you want some 4.3.1 repacks done i can do them? or if you want some experience, i have the tools to swap ramdisks on windows in my signature that you could use...
In CM ROMs I get crazy data switches from 3g to E and G. Everything is good so far. Time will tell...
Sent from my Optimus 4X HD using Tapatalk
---------- Post added at 01:22 AM ---------- Previous post was at 01:08 AM ----------
penguin449 said:
If you want some 4.3.1 repacks done i can do them? or if you want some experience, i have the tools to swap ramdisks on windows in my signature that you could use...
Click to expand...
Click to collapse
If you can then that would be great. A download for each CM ROM would open up custom ROMs like never before.
Sort out the SD card/internal memory paths and stock ROMs would be not worth installing.
Sent from my Optimus 4X HD using Tapatalk
penguin449 said:
If you want some 4.3.1 repacks done i can do them? or if you want some experience, i have the tools to swap ramdisks on windows in my signature that you could use...
Click to expand...
Click to collapse
if you've got the time and the will, be my guest - however, i don't think it's quite worth it. Not many people have this issue, and those that do would be better off fixing it by themselves then downloading aged nightlies for the rom they're looking for.
MilkyJoePD said:
In CM ROMs I get crazy data switches from 3g to E and G. Everything is good so far. Time will tell...
Click to expand...
Click to collapse
hm, switches from 3g to 2g seems to show that there is a bad connection where you're at. try enabling 2g only or 3g only in custom rom options or quick tiles, most roms support it these days. that should save your battery for few more %.
Just wanted to say that since replacing the file I haven't had to reboot once to get SMS or network to work.
That's over a month, whereas I was having to reboot about every 2 days.
The G/3G switching has improved, but still more sensitive than stock.
Sent from my Optimus 4X HD using Tapatalk
hey what if.... there is no x3ril.smali?XD there is only ril.smali or many others
edit: its ok there just x3ril was missing
I'm on a odexed ROM (mokee 4.2.2 release) so I don't know what to do with classes.dex file multitool generates.It was meant to be used for deodexed telephony-common.jar files.So I tried these steps:
1_)deodex the ROM (using deodexer 4.3),
2_)implent RIL
3_)odex the ROM(using universal odexer 6.3.1) again which I failed to do as something was wrong with decompiling before odexing.This is probably happening due to deodex process.
I got bootloop after odexing the ROM.So I'm curious if there is a way to do this on an odexed jar file without having to deodex first.
I also tried to simply delete the odex & jar file and replace it with deodexed and eprj RIL implented jar file but the rest of the ROM was odexed so it gave me a bootloop.
I don't know much about these stuff, but I did my best searching for a solution and I'm out of ideas.All I want is to have an odexed rom with EPRJ RIL implented, I'd appreciate any help
ottomanhero said:
I'm on a odexed ROM (mokee 4.2.2 release) so I don't know what to do with classes.dex file multitool generates.It was meant to be used for deodexed telephony-common.jar files.So I tried these steps:
1_)deodex the ROM (using deodexer 4.3),
2_)implent RIL
3_)odex the ROM(using universal odexer 6.3.1) again which I failed to do as something was wrong with decompiling before odexing.This is probably happening due to deodex process.
I got bootloop after odexing the ROM.So I'm curious if there is a way to do this on an odexed jar file without having to deodex first.
I also tried to simply delete the odex & jar file and replace it with deodexed and eprj RIL implented jar file but the rest of the ROM was odexed so it gave me a bootloop.
I don't know much about these stuff, but I did my best searching for a solution and I'm out of ideas.All I want is to have an odexed rom with EPRJ RIL implented, I'd appreciate any help
Click to expand...
Click to collapse
unfortunately, i encountered the same issue, and it's beyond my knowledge on what to do with odexed roms. i bypassed the issue by using a nightly which came after the stable was released (not sure if there are any for mokee though)
Discontinued.
Awaiting for thread deletion.
Thanks...Nice work after your miui 5 ROM
Help please..
Need someone who can risk his device by testing this ROM......
Happy holi.....
Happy holi my friends...
May this holi bring lots of Colors in your life!! and in mine too.
Kunal Gautam said:
Need someone who can risk his device by testing this ROM......
Click to expand...
Click to collapse
I tried to install but it gives error 7 i think update.script should be rechecked.
Deep_dhimaan said:
I tried to install but it gives error 7 i think update.script should be rechecked.
Click to expand...
Click to collapse
Thank you very much, i've understood whats the problem( as a pm by ashkineeeeee).
New update coming soon. Stay tuned.
Hey bros...
so there were some problem with permissions, it seems that it is fixed now..
Flash the ROM and review here....
----------------------edit 1---------------------
dont flash the rom now!!!
Some files are missing in boot.img
how stupid i am!!
------------------------edit 2-----------------------
Flash it now!
Last build not installed,error 7.
mels01 said:
Last build not installed,error 7.
Click to expand...
Click to collapse
Logs,screenshots?
Try installing from internal storage... Or update your recovery to the latest one by android andi...
Thanks!
Hey, I would like to help out, can I have the link to the ROM?
theportal2 said:
Hey, I would like to help out, can I have the link to the ROM?
Click to expand...
Click to collapse
I agree this message is a bit long but it is worth reading.
- Thanks, but sorry. Even if I give you the links and even if spend your precious time you would only be able to fix the error 7.
- Actually I've already fixed that(or know what's the issue atleast). There are files that are missing from the directories that are listed in the updater script. They cannot be deleted as the original base ROM I compiled was from UA(unlegacy android) that are based on the newer sources.
- Some files that are required for MIUI are also missing.
- Boot.img is incomplete. Which will result in bootloop even if I upload the error 7 fixed ROM.
- I am giving my board exams that are one of the biggest exams in India. And I cannot afford to score less in these.
- All I need is a older base ROM ,CyanogenMod 11 made around may of 2016. And also it must support init.d because the port ROM requires that.
- I've taken permissions from the maker of the port ROM. He has allowed me to proceed.
- All I need is permission from Android-Andi, as only he has older CM ROMs.
- I cannot compile because older sources are not available or maybe I am not known to them
Hope you understand. Thank you.
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Links
Kunal Gautam said:
I agree this message is a bit long but it is worth reading.
- Thanks, but sorry. Even if I give you the links and even if spend your precious time you would only be able to fix the error 7.
- Actually I've already fixed that(or know what's the issue atleast). There are files that are missing from the directories that are listed in the updater script. They cannot be deleted as the original base ROM I compiled was from UA(unlegacy android) that are based on the newer sources.
- Some files that are required for MIUI are also missing.
- Boot.img is incomplete. Which will result in bootloop even if I upload the error 7 fixed ROM.
- I am giving my board exams that are one of the biggest exams in India. And I cannot afford to score less in these.
- All I need is a older base ROM ,CyanogenMod 11 made around may of 2016. And also it must support init.d because the port ROM requires that.
- I've taken permissions from the maker of the port ROM. He has allowed me to proceed.
- All I need is permission from Android-Andi, as only he has older CM ROMs.
- I cannot compile because older sources are not available or maybe I am not known to them
Hope you understand. Thank you.
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Click to expand...
Click to collapse
Have you seen this CM 11? https://forum.xda-developers.com/galaxy-tab-2/7-inch-development/rom-cm-11-0-galaxy-tab-2-t3737392
Just made last month by @Deltadroid
Links are removed because *the ROM is not complete yet*.
Thanks, but I need to confirm a few things before I could use a ROM(includes init.d support and a bunch of other things). Also, it is very important that deltadroid provide me permission to use his ROM.
Thank you!
Regards,
KG
-----_edit_--------
I just saw deltadroid's thread, the title clearly says that the ROM is for p3110. I want to make a unified one. I need a ROM made with unified device tree.
If I do port, it will only work on p3110 and maybe on every 7" device. I don't want do this.
Sorry, but yeah thanks!
Just wait till 3 april 2018. Most probably I will upload.
Edit 2
Or I must say it an update. 75 percent of the work is done. Somehow I managed to get a base ROM(only I know how). Only build.prop editing and Updater script editing work left(these are the most difficult BTW).
Update coming soon. Stay tuned.
I've updated the links. I've uploaded the new ROM. I've done with porting(i guess). I've used a lot of time.
Flash and review!
Kunal Gautam said:
I've updated the links. I've uploaded the new ROM. I've done with porting(i guess). I've used a lot of time.
Flash and review!
Click to expand...
Click to collapse
No wonder the ROM doesn't work.... Security patch is in a wrong format.
"ro.build.version.security_patch=2080-17-March"
It should be, "ro.build.version.security_patch=2018-03-01"
or,
"ro.build.version.security_patch=2018-03-05"
And this, hardly doubt this will work, but idk.
"ro.build.date.utc=999999999999"
Mistakes....................
EDIT**** Build id should be the app id: example lets say the id is 678, on build.prop, it would say 678.
you have, "ro.build.id=KUNAL"
secretwolf98 said:
No wonder the ROM doesn't work.... Security patch is in a wrong format.
"ro.build.version.security_patch=2080-17-March"
It should be, "ro.build.version.security_patch=2018-03-01"
or,
"ro.build.version.security_patch=2018-03-05"
And this, hardly doubt this will work, but idk.
"ro.build.date.utc=999999999999"
Mistakes....................
EDIT**** Build id should be the app id: example lets say the id is 678, on build.prop, it would say 678.
you have, "ro.build.id=KUNAL"
Click to expand...
Click to collapse
You, sir, definitely have a lot to offer. I am afraid that this is not the actual problem. By now, I surely understand the importance of logs. Would be very helpful if someone could arrange me them.
And about your post it seemed really rude, raw, insulting and manipulating to me. But however, helpful. It makes it really hard to continue developing for a 6 years old Tab, with hardware that has nothing to offer in 2018. At least, I am trying.
Since, this was an Alpha build(because I moved sources) these problems are sure to arise. I did the same(build.prop things) with my kinda successful ROM MIUI 5(see it in the 7" forums).
I guess you haven't tasted port ROMs yet. They are hard to build. Alike your compiling ones, you have source, type some commands, turn your computer on for about 5 hours, when done upload it.
I am sure you must have did trail and error (in chemistry and math) porting ROMs is just the same. I am sure, that as a developer, you must know what logs actually mean.
But whatever, thank you for you review(insult I guess).
Kunal Gautam said:
You, sir, definitely have a lot to offer. I am afraid that this is not the actual problem. By now, I surely understand the importance of logs. Would be very helpful if someone could arrange me them.
And about your post it seemed really rude, raw, insulting and manipulating to me. But however, helpful. It makes it really hard to continue developing for a 6 years old Tab, with hardware that has nothing to offer in 2018. At least, I am trying.
Since, this was an Alpha build(because I moved sources) these problems are sure to arise. I did the same(build.prop things) with my kinda successful ROM MIUI 5(see it in the 7" forums).
I guess you haven't tasted port ROMs yet. They are hard to build. Alike your compiling ones, you have source, type some commands, turn your computer on for about 5 hours, when done upload it.
I am sure you must have did trail and error (in chemistry and math) porting ROMs is just the same. I am sure, that as a developer, you must know what logs actually mean.
But whatever, thank you for you review(insult I guess).
Click to expand...
Click to collapse
FYI, I port ROMs. It was pointers what to fix, if you wanted to get this ROM better, than it is already.
Kunal Gautam said:
(...)
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Click to expand...
Click to collapse
Sorry, I won't give permissions after different people used my ROMs as base in the past without permissions. Hope there is a learning affect....
Since i love OpenSource: Sources are available on every official GitHub (slim, Omni, Lineage, UA) and up to date (note: I wouldn't have to do this, I could keep all device trees private but I am updating them for everyone - always). You'll have to compile your own base ROM to use for such port ROMs (I am not a fan of).
Android-Andi said:
Sorry, I won't give permissions after different people used my ROMs as base in the past without permissions. Hope there is a learning affect....
Since i love OpenSource: Sources are available on every official GitHub (slim, Omni, Lineage, UA) and up to date (note: I wouldn't have to do this, I could keep all device trees private but I am updating them for everyone - always). You'll have to compile your own base ROM to use for such port ROMs (I am not a fan of).
Click to expand...
Click to collapse
Thank you. For at least replying. You works will always be appreciated. Now, I am gonna close this thread. Thanks again!