Related
Hi everybody,
I just compiled a stock AOSP 2.3.7 ROM from aosp sources as one of the team members got recently a P990 and I decided to do some stuff for this device although I don't own one. This is where you can help as I can't test myself.
I have attached the build.prop already for those who are interested in having a look into it.
The ROM is based on GWK74 Android 2.3.7 and has yet no modifications added compared to the stock AOSP project. You can participate and share your ideas by means: leave / stay with launcher2 / gallery3d / stock camera+browser-app or replace those with better alternatives. I want to make this ROM barebone-like to provide you a highly customizable ROM. As like you do with stock CyanogenMod ROMs you will have to add the CM-GAPPS on your own via CWM. I won't include them into the ROM so you could even modify the gapps-package and adjust it to your needs.
As I am actually not familar with the available kernels and how they perform on P990 I will include the built-in cm-kernel.
People wanna help with testing this please leave a message on this topic (no PMs plz). The first download links should appear this evening / tonight (UTC+1) as I am going to do a final fresh compile now. Those leaving a message will receive the link by PM. Once I receive positive feedback I will make it public.
The sources I used:
CM-github (modified LGE P990 + star-common device tree for AOSP)
Android Open Source Project
About me:
neopeek - primarily focused on XDAndroid project and making ROMs based on the XDAndroid project.
Im in
10chars
Me too
Sent from my Optimus 2X using XDA App
Count on me!
I'm in mate!
Sent from my LG-P990
ok you all got a private message with the link!
Hello,
It's a good start. I can't install it via CWM 5.0.2.7. I will try via CWM 5.0.2.0.
ok thx for providing feedback. Might require some fix to the updater-binary or updater-script. Lemme check this...
Same here, status 0
No idea what that means though
Error status 0 is caused by a wrong updater-binary. My fault! Misplaced some files while packaging it. I have re-uploaded the ROM now again. This time I used CM7 META-INF but added my own updater-script. To assure other issues the zip is unsigned now. So you will have to disable "signature checks" in CWM, too. Don't forget to wipe data/cache partitions in CWM, too.
Can I test this rom?
Count on me!
It's not modified like CM, just pure Android 2.3.7? Hmm I think It's a good idea, if you will be able to fix CM's bug (of course if there are here) it will be maybe one of the best rom. You can count on me too though.
Free to test if you need more testers for feed back? ;-p
Waiting eagerly for build, wanna give a shot
I have put this project on hold for now. I flashed latest Austrian ICS build to my device and continue using it as my Kindle reader on my travels. IF somone manages to fix the two issues with kernel, send me a message and I'll continue working with the repository. But for now I'm not thinking nor touching the subject before Easter. Thank you for participating for now
I've started porting Ubuntu-touch dev-preview to the Galaxy Tab 7.7 (3g). If you do not understand it already, you flash this at your own risk. There is now also a Ubuntu-touch specific device page here: https://wiki.ubuntu.com/Touch/Devices/p6800. I'll try to keep this thread and the Ubuntu devices page as close to each other as possible.
Big thanks to Daniel_hk for helping with boot.img Now It can be booted, but the screen is still black
Also, without working wifi and display, the preview is basically unusable... Next steps should be these:
1. Get wifi drivers working.
2. Get display drivers working.
Code:
[email protected]:/# uname -a
Linux localhost 3.0.15-CM-g1dc3074 #2 SMP PREEMPT Wed Mar 13 00:43:37 EET 2013 armv7l armv7l armv7l GNU/Linux
Repositories:
Latest release tagged with: "v0.3", not tested!
https://github.com/dun1982/android_device_samsung_p6800
https://github.com/dun1982/android_kernel_samsung_p6800
Download
cm-10.1-20130312-UNOFFICIAL-p6800.zip
Daily Ubuntu image: http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/
Installation
Install CWM 6.0.2.8
Wipe data/factory reset
Wipe cache partition
Flash cm-10.1-20130312-UNOFFICIAL-p6800.zip to device
Flash quantal-preinstalled-phablet-armhf.zip to device
Reboot
Starting to use
Then it gets interesting (Black sreen for now now Run the following commands in your desktop system:
Code:
adb root
adb shell
ubuntu_chroot shell
You should have now root access inside your tabled. Continue with this wiki next
What works
Ubuntu-touch dev-preview is flashable.
It boots!
Known Issues
Kernel is based to the CyanogenMod/android_kernel_samsung_smdk4210, but it is a mess. So forked it, took code here and there (mostly from locerra's JB build).
Kernel is based 3.0.15 and no newer one available (yet).
Most of the drivers in kernel had to be turned off, because build was not succeeding...
bluetooth: Doesn't work
audio: Dock audio doesn't work.
hwcomposer: HDMI dongle doesn't work.
wifi: Doesn't work.
camera: Doesn't work.
.. and lot of kernel level bugs for sure.
Displaydrivers are not working (yet).
Release notes
Version 0.2 (13.03.2013) - Now it boots, see release notes
Version 0.1 (07.03.2013) - Intial release, nothing works
Credits
BIG THANKS to daniel_hk for solving the boot.img problem for me.
Anyone who has worked previously with the device/kernel source.
locerra (for getting CM10.1 to flashable state).
wowww!!! thank you !test now:victory::victory:
Placeholder for future.
Re: [ROM][P6800]Ubuntu-touch dev preview(02.03.2013)
Not 6810 versión?
AUs
el_campi said:
Not 6810 versión?
AUs
Click to expand...
Click to collapse
I cannot test it for anything else. The kernel sources are from CM10.1 that was in use from locerra, so in theory it should work with i815 and with p6810 as well. But I cannot give you any guarantees...
And also before I get this build to even start with my device, I do not think that sharing image would help anyone. But if you are a developer, I would like to talk with you on issues that I might have missed or done wrong. So contact me
Re: [ROM][P6800]Ubuntu-touch dev preview(02.03.2013)
any update?
Sent from my GT-P6800 using xda premium
Not much. The generated image is missing /data/ubuntu completely and that is the reason why the image does not boot. I got also flu and fewer, so I have had not that much time after the weekend to look on the issues on that.
I'm also waiting if I get any answers from Ubuntu touch emailing list regarding the problem and where to look for answers, but my quess is that it has something to do with the devices fstab file...
Good news everyone!
Just got a very good answer the problem I had with the /data/ubuntu-folder missing from the image. There was no image provided for the actual Ubuntu at all by the build-process...
When I get home from work, I'll try to find time to look into the build process if I can include the actual Ubuntu image to the ready made image and then release it after I get my device to boot. But it seems that I got the right nudge forward for this now :highfive:
Hmpf, still not booting. Now the /data/ubuntu logs are unmodified, which would point towards kernel or fstab-issue (ie. /data/ubuntu is never used...).
Re: [ROM][P6800]Ubuntu-touch dev preview(02.03.2013)
Good job :thumbup::thumbup::thumbup::thumbup::thumbup::thumbup:
Sent from my GT-p6800 using xda premium
Doh... still not working... Any ideas anyone?
Ok, new version build from different repositories (thx, danile_hk for tip).
I'll test the new image this evening when I get back to home, and I have my fingers crossed that I can get the device to boot up and even display something useful. After that I can start looking for ubuntu developemnt
New version did not work, but then Daniel_hk gave me working boot.img. So now I need to find out what the heck is wrong with my repository and fix it so that I can get working boot.img from start and also the device configuration has issues. Both repositories are currently out of sync I'm afraid
dun1982 said:
New version did not work, but then Daniel_hk gave me working boot.img. So now I need to find out what the heck is wrong with my repository and fix it so that I can get working boot.img from start and also the device configuration has issues. Both repositories are currently out of sync I'm afraid
Click to expand...
Click to collapse
Also, without working wifi and display, the preview is basically unusable... Next steps should be these:
1. Get wifi drivers working.
2. Get display drivers working.
It seems that I hit the wall (again) with the mentioned big issues.
For now, I keep some sabbatical from Ubuntu Touch things (ie. I flashed ICS Austria to my device) and use it as my Kindle reader again.
If by miracle I get more info regarding how to get the Kernel working with Ubuntu Touch, then by allmeans I continue working with this project. So far it just seems that making a working image, is out of my hands currently.
At least you had a go. Thanks for your efforts, and hope you might have another crack at it later on.
I'm feeling a little bit that way right now too, and put my ICS kernel on the back burner. I think I'm trying to multitask a little too much at times....
Yep, a break is what you need, maybe some clarity will come after you've had a chance to recharge.
Sent from my GT-I9300 using xda premium
It's very nice to see you took up the big responsibility to make this superb device to be usable again! it has great specs, really. KUDOS bro!!
Any update on this development?
ZhenMing said:
Any update on this development?
Click to expand...
Click to collapse
Not much, I have had no interest to spend time with this topic because I have been very busy IRL. After I get my new house renovated fully and get my job tasks done, I wont be spending much time with this project. Feel free to use any sources provided in this thread to further advance the subject.
But this wont go forward that much, if the GT-P6800 wont get official CM10.1 update...
It works?
Hello guys:laugh:
I searched every forum thoroughly but didn't found a proper and working solution for Xperia devices
I am trying to make a custom ROM from stock using dsixda kitchen
I used stock 12.1.A.201 as the base ROM
I believe that it's either the updater script error or kernel probelm as I am using stock kernel and my zip is like this
Data
META-INF
system
boot.img
check_data_app
Click to expand...
Click to collapse
This happens when rom is created
De-odexed it rooted it and added X-Reality engine and created the rom
First on installing I got error of status 0 so I changed my update binary file from same de-odexed version from this link http://forum.xda-developers.com/showthread.php?t=2704312 by @dipesh1502 (thanks to him for that awesome rom)
Next I am getting error status 7
ROM Starts flashing then it comes to this part
formatting system bla bla
expected 5 args got 3
Click to expand...
Click to collapse
something like that and then it stops on error status 7
here is the updater-script please have a look. I really want to create this ROM. Please help
Updater-Script Download
here is my build prop build.prop download
Help guys please I'll be highly grateful
My device is C5302 rooted and unlocked bootloader with 12.1.A.205 stock kernel
EDIT : Got past the error status 7 now ROM gets installed
But unfortunately now it ends in a bootloop :/ Got stuck on Sony splash logo and then reboots constantly :/
Had a nandroid backup ready x)
Had to flash the ftf file over and over again. :/
Phone is allright just want to catch this error of bootloop.
I changed kernel with the dipesh1502's ROM but still no luck. Modified Updater script but still no luck. help me I am soo confused and screwed!! :'( :'(
My new Updater-Script
There's a HUGE difference in creating boot animations and creating a ROM.
Don't expect to teach yourself how to make a ROM in just a few days.
It takes, weeks, months, years...
If you're mainly planning to make some exterior changes, which I think you're currently doing, I would focus on making complete themes and not ROMs.
People are not waiting for a ROM which is already available but that looks somewhat different and maybe has some extra or removed apps.
Regarding your problem, I will not be able to help you since I don't have that kind of knowledge.
Anyway, good luck!
Gamm86 said:
There's a HUGE difference in creating boot animations and creating a ROM.
Don't expect to teach yourself how to make a ROM in just a few days.
It takes, weeks, months, years...
If you're mainly planning to make some exterior changes, which I think you're currently doing, I would focus on making complete themes and not ROMs.
People are not waiting for a ROM which is already available but that looks somewhat different and maybe has some extra or removed apps.
Regarding your problem, I will not be able to help you since I don't have that kind of knowledge.
Anyway, good luck!
Click to expand...
Click to collapse
Thanks for the reply.
Yeah I know that it's not easy to create ROM and also it takes a lot of time. I am ready to give it a shot
I am just making some small changes just for my sake I'll be using this ROM personally for my own use I know that there are a thousand times better ROM's than mine
Anyway glad you considered my probelm.
Bootloop can be cause by:
- Wrong permissions
- Corrupt installation
It is nice if you collect either the last_ksmg or logcat when bootlooping. (if possible)
~~Regard
---------- Post added at 08:08 PM ---------- Previous post was at 08:04 PM ----------
But first:
Share me the .zip you have created perhaps I can take a small look
~~ Regards
mrjraider said:
Bootloop can be cause by:
- Wrong permissions
- Corrupt installation
It is nice if you collect either the last_ksmg or logcat when bootlooping. (if possible)
~~Regard
Click to expand...
Click to collapse
Thanks for the reply
Can you please have a look at my new updater-script and tell me what is wrong?
I will surely try to get logcat but before that if you can just analyze this updater-script and pinpoint the mistakes it'll make my work a lot easier.
Thanks in advance :good:
Sent me the entire .zip file instead (but start with updater-script)
~~Regards
mrjraider said:
Sent me the entire .zip file instead (but start with updater-script)
~~Regards
Click to expand...
Click to collapse
Sure thing I'll
I am compressing it to maxium extent using KGB archiver and it'll become around 10~20 mb only
It's still compressing so it'll take some time before it reaches it's max compression.
I'll surely send you asap
I have ported Oreo for Mi mix , wifi working , sound , bluetooth , camera , nfc , android pay but i keep getting com.android.phone error and don´t know how to fix it. Yes im noob and i have learnt to compile using xda guides and youtube tutorials so please dont be too hard with me i beg you . Thanks for the help . I´ll give donations to helpers.
Hi @YazumiWuHung,
sorry with that little information it's somewhat impossible to assist you :_/
I'd like to advice the 2 things as followed:
- head over to the ROMs section (https://forum.xda-developers.com/mi-mix/development) and post your question and if possible an downloas/test possibility there
- create at least an log of the error in the timeslot it apperars -> HowTo: https://developer.android.com/studio/command-line/logcat.html
Good luck!
Could be any (but not limited to) of the following:
- permission/folder issues in ramdisk (for example for the modem part)
- missing/incorrect config xmls in overlay (framework, or Phone package)
- missing/incorrect parameters in *props
As suggested by raupe, a logcat could point in the right direction.
willing to test for you if you want that..
thanks for your efforts to bring oreo to us!
Found Nazmul hasan on Androidfilehost.
He has worked on mi mix Oreo.
https://androidfilehost.com/?fid=745849072291680983
He might help you.
All the credits goes to respective developers.
I have not tried the rom yet so don't ask me what's working or not.
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!