In light of the newly-minted LuneOS alpha release, I was wondering if anyone had experience dualbooting webOS on their Galaxy Nexus? I know it's possible to do so with Android-based ROMs, but I want to keep my CM nightlies as a fall-back, especially since the LuneOS is in such an early stage and technically does not officially support the device (they're looking for community support *hinthint devs*). If you do, please drop a note with your experience in this area! Thanks in advance. :good:
drfandroid said:
In light of the newly-minted LuneOS alpha release, I was wondering if anyone had experience dualbooting webOS on their Galaxy Nexus? I know it's possible to do so with Android-based ROMs, but I want to keep my CM nightlies as a fall-back, especially since the LuneOS is in such an early stage and technically does not officially support the device (they're looking for community support *hinthint devs*). If you do, please drop a note with your experience in this area! Thanks in advance. :good:
Click to expand...
Click to collapse
Well,it would be cool,even with sailfish os,that i really love
Anyway for everybody who wants to try webos (LunaOs) http://webos-ports.org/wiki/Maguro_Info
I just saw the news on Engadget and came here to see if anyone was talking about this. I'm going to try this out since my GNex is mainly just sitting in a box now. I miss webOS.
The only thing I wonder about is that I have a Verizon GNex. If I don't use it for calls or anything, does it matter if I flash the Maguro version? I remember I was in the same boat with the Ubuntu phone port but I think I waited for the Toro port. I can't remember.
jsgraphicart said:
I just saw the news on Engadget and came here to see if anyone was talking about this. I'm going to try this out since my GNex is mainly just sitting in a box now. I miss webOS.
The only thing I wonder about is that I have a Verizon GNex. If I don't use it for calls or anything, does it matter if I flash the Maguro version? I remember I was in the same boat with the Ubuntu phone port but I think I waited for the Toro port. I can't remember.
Click to expand...
Click to collapse
Wondering this as well.
they had, and still have the best multitasking on a mobile device i've ever used. it was just so fluid and intuitive. some of their features they incorporated are still ahead of their time today
x000x said:
they had, and still have the best multitasking on a mobile device i've ever used. it was just so fluid and intuitive. some of their features they incorporated are still ahead of their time today
Click to expand...
Click to collapse
Agreed. Has there been any other phone that uses a gesture area like they did? I loved that.
jsgraphicart said:
Agreed. Has there been any other phone that uses a gesture area like they did? I loved that.
Click to expand...
Click to collapse
I looked for a long time, but nothing recent. there was one thing kind of similar, a few years back called 'itching thumb' http://www.xda-developers.com/android/use-itching-thumb-to-multitask-in-android/ but was discontinued long ago.
Yeah, well I just checked the comments on their official release post, and after some helpful replies I can (sadly) announce that there is no dual-boot support. Also, the latest build they have is a couple weeks old, since they no longer have a maintainer for the device The post is here, if any of you want to skim it . So at this point it's either flash a build that's dated, without a fall-back that would come with dual-booting, or wait and see
drfandroid said:
Yeah, well I just checked the comments on their official release post, and after some helpful replies I can (sadly) announce that there is no dual-boot support. Also, the latest build they have is a couple weeks old, since they no longer have a maintainer for the device The post is here, if any of you want to skim it . So at this point it's either flash a build that's dated, without a fall-back that would come with dual-booting, or wait and see
Click to expand...
Click to collapse
There's a Sept. 1st build there. More towards the Center.
http://build.webos-ports.org/luneos-testing/images/maguro/
There's a Sept. 1st build there. More towards the Center.
Click to expand...
Click to collapse
Yes, I just noticed haha my bad. I was just paraphrasing a comment off of the post I linked to. Shame there's only dual-booting available on the Touchpad (for now at least). I'll probably wait until the next stable release or so before diving in.
jsgraphicart said:
I just saw the news on Engadget and came here to see if anyone was talking about this. I'm going to try this out since my GNex is mainly just sitting in a box now. I miss webOS.
The only thing I wonder about is that I have a Verizon GNex. If I don't use it for calls or anything, does it matter if I flash the Maguro version? I remember I was in the same boat with the Ubuntu phone port but I think I waited for the Toro port. I can't remember.
Click to expand...
Click to collapse
im flashing it on a toroplus right now, gonna let you guys know how it goes when it finishes. on a related note, make sure to wipe /system before you flash, because the updater script doesnt do that. i had cm11 installed on there before and forgot to do it, so im reflashing clean now.
also, it looks like at least some of the android file system is retained, so that means we may be able to get data working by pulling libs from a 4.2.2 rom. dont quote me on that, ill try it and see what happens when i get this thing to boot. I pulled apart the boot.img and nothing seems to be stopping us there either from what I can tell.
edit: as much as i wish this worked, dont waste time flashing it if your not a maguro device. doesnt boot on toroplus, prolly wont boot on toro either.
whoshotjr2006 said:
im flashing it on a toroplus right now, gonna let you guys know how it goes when it finishes. on a related note, make sure to wipe /system before you flash, because the updater script doesnt do that. i had cm11 installed on there before and forgot to do it, so im reflashing clean now.
also, it looks like at least some of the android file system is retained, so that means we may be able to get data working by pulling libs from a 4.2.2 rom. dont quote me on that, ill try it and see what happens when i get this thing to boot. I pulled apart the boot.img and nothing seems to be stopping us there either from what I can tell.
edit: as much as i wish this worked, dont waste time flashing it if your not a maguro device. doesnt boot on toroplus, prolly wont boot on toro either.
Click to expand...
Click to collapse
That's too bad. What are you getting when it tries to boot? Have you let it sit for a while before coming to that conclusion? Maybe it doesn't have any sort of booting indication.
Update: I ended up going for it, and flashed the stable build onto my maguro. Worked, but none of the apps would open again after I had closed them for some reason (If I wanted to open Preware 2 again, I had to reboot the device...). The dev build wouldn't boot at all after flashing, so I'm running on the August 10th stable build.
jsgraphicart said:
That's too bad. What are you getting when it tries to boot? Have you let it sit for a while before coming to that conclusion? Maybe it doesn't have any sort of booting indication.
Click to expand...
Click to collapse
sorry it took so long to reply, but yep i waited 10 minutes for adb or any indication that it was going to boot. after reading drfandroid's post about getting august 10ths build to boot and not being able to get the newest nightly to boot, im thinking thats my problem too. ill try to use the one mentioned and see if i get different results.
whoshotjr2006 said:
sorry it took so long to reply, but yep i waited 10 minutes for adb or any indication that it was going to boot. after reading drfandroid's post about getting august 10ths build to boot and not being able to get the newest nightly to boot, im thinking thats my problem too. ill try to use the one mentioned and see if i get different results.
Click to expand...
Click to collapse
Well that sucks. Hopefully someone picks up development for this device. I'd like to try it out eventually. I have an HP Touchpad but it has Android on it as well. I havent looked into it yet but installing this might need a full wipe. I don't want to go through the hassel of starting all over again. lol
jsgraphicart said:
Well that sucks. Hopefully someone picks up development for this device. I'd like to try it out eventually. I have an HP Touchpad but it has Android on it as well. I havent looked into it yet but installing this might need a full wipe. I don't want to go through the hassel of starting all over again. lol
Click to expand...
Click to collapse
You're right, flashing it on your nexus pretty much requires a full wipe lol. The Gnex doesn't have dual-boot capability for LuneOS (yet!! ). I asked in the comments of the announcement post. Fingers crossed for that, though! Really hoping a dev steps out and continues the project, even if it's just on the side.
whoshotjr2006 said:
sorry it took so long to reply, but yep i waited 10 minutes for adb or any indication that it was going to boot. after reading drfandroid's post about getting august 10ths build to boot and not being able to get the newest nightly to boot, im thinking thats my problem too. ill try to use the one mentioned and see if i get different results.
Click to expand...
Click to collapse
Any luck with the August 10th build? My build can't activate developer options (Settings--> Developer Options, flicked the switch, still says "Developer mode is disabled"-->entered Konami Code into search, tapped on the dev mode result, nothing happened), so I can't activate USB Debugging or anything like that. On top of that, the phone takes forever to even boot into the Google screen, and I can't get into Recovery or Fastboot mode. In essence, even if I wanted to re-attempt to flash the nightly or go back to Android, I can't. I was hoping to go try the PA 4.6 Beta on my Gnex, so I was a bit gutted. Any ideas??
drfandroid said:
Any luck with the August 10th build? My build can't activate developer options (Settings--> Developer Options, flicked the switch, still says "Developer mode is disabled"-->entered Konami Code into search, tapped on the dev mode result, nothing happened), so I can't activate USB Debugging or anything like that. On top of that, the phone takes forever to even boot into the Google screen, and I can't get into Recovery or Fastboot mode. In essence, even if I wanted to re-attempt to flash the nightly or go back to Android, I can't. I was hoping to go try the PA 4.6 Beta on my Gnex, so I was a bit gutted. Any ideas??
Click to expand...
Click to collapse
yep no luck for me here, mine just wont boot into it at all. I can still access fastboot though, holding both volume buttons from and power from completely off doesnt get you into fastboot? if your volume button hardware has gone bad, i know you can buy new on ebay for cheap, might have to do that. sorry to hear about your problem, and I hope you get it fixed somehow.
Related
Update 10-5
To make steve jobs roll over in his grave, I give you CM7.
Now to make this perfectly clear.....
I did not compile the kernel.
As it is, I was NOT going to release this until I completed the kernel so that it said MY name in "about"
We clear?
JT1134 did the kernel. I updated my source to compile the same kernel. I built a more or less custom CM7 system, did my crazy thing to it, however I used one of MY systems I built on my machine.
I am saying this, because I dont like releasing **** that I feel I didnt make 100%. Alot of people are ok with this, I view it differently.
Its easy guys.
Flash using CWM.
Get CWM anyway you have to on the tab, Im going to say wipe everything first, mount system, flash the rom, then do a full wipe again, should boot. I myself had issues with initial boot up, but i realised system needed to be mounted.
3G along with everything else works.
Download BTL CM7 RIGHT HERE
Oh, the DPI is set to the 185 I like, sorry.
Changes Ill be making this week/weekend....
Adding the audio to boot animation
System UI tweaks
Kernel with MY name on it out of respect to JT1134
A second "stripped AOSP version.
Sorry it has been so long for this release, ive been running it myself for almost a week.
Update 9-26
Back on the game 100% right now.
I took a break as I was taking this project very personal, and that was lame.
I was having an issue with the build being stable, all based on the data partitions.
I am going to sync the latest material off the interwebs today, try a few new builds to release, I am hoping to get something out today, If the kids let me work enough.
I am going to reach out and help Boush, and JT with their build, and see if I can get help with mine, cause in the end, it's not a race, it's an open source community.
I am building one right now, so we will see how it goes, I am down to only 1 tab right now, and while it is the Sprint model, i caqnt test 3g till i get my verizon one back from samsung.
After I am done with CM7, I will probably sell 3 of the tabs off, and switch over to writing workflows.
I, am tired.
So, before I get to the dirty details everyone wants, the more important stuff up front.
Spacemoose.
A friend, my pal, my Yoda. None of this, hell none of my roms would be here if it wasnt for him. He helped in so many ways, almost all ways up until the end. I hope next week is better for you.
Technomancer.
For the code, the answers, the help, the help you gave Dan, and then me when i picked this back up. Still trying to reach you via GTalk, however, you to are another major help, if not the reason i have the ability to build this stuff.
=================================================
CyanogenMod7 for Galaxy Tab CDMA {SPRINT AND VERIZON}
I dont know where to start, this is kind of a big thing, bigger than the 2 GB roms i did.
This is built from source, based on the GSM source with many many tweaks, including tweaks I had to do last night, and even today to get it to run for 5 minutes on my tab.
This is Alpha build quality, what can you expect, let me tell you..
This is not daily driver material.
This may, or may not run for more than 5 minutes, though I do have a streak of 60 minutes today.
However it boots, and loads the OS, and allows navigating throughout the system, but can and probably will randomly reboot.
I know what the issue is, it is kernel level, I know exactly what it is, and will be all over it tomorrow starting 6am cst.
Whats Working.
?? good question, never took time to try stuff
Launcher Pro if installed via ADB
Whats Broken.
ADW Launcher (touch calibration is jacked up from ADW)
Calibration? (had to edit build prop to rotate screen 180 so launcher pro would register my touch properly.
I have run through the system today a few times till i ran the battery down, and it worked, no idea on 3G or wifi as at that time I was worried about basic functionality.
Stages of work....
Effect tomorrow I will build a few new kernels, including a new one that should place CM7 directly onto the SD card, test those out, and get that patch done I need to. I do feel that patch is 98% of the problem.
I will then address any bug reports, start a list in another reply i will save, and cross off each one as fixed to eliminate future confusion.
There may be nightlies depending on how much I can accomplish in a 16 hour day.
This will be stable, and perfect. Has to be, it's CM7
Instructions for installation.
Flashing zip via CWM
Place on SD card, wipe everything, then choose zip, flash, and for good measure, wipe again after the flash.
Flashing with Heimdall
Ill release a heimdall version tomorrow by noon.
Make sure to wipe data, cache, dalvik, fix permissions, just run with it, better to be safe, than sorry.
Links
Download Link for Flashable Zip
Reboot and enjoy for as long as you can, I can not test how it runs on other tabs vs my daily driver right now.
CM7 Source.....
Let me finish this alpha to a stable beta, organise my source's, make sure all my patches are in, and I will be more than happy to put it all up on my Github. Placing my current source up right now, might cause problems. I will also post instructions like Technomancer did. Yall know i love to edit my posts, lol so check back often.
If you like my work, feel free to donate.
....
Placeholder
2nd placeholder
3rd placeholder, and where I will be putting all sources, instructions, and patch information at.
Man....I am exhausted big time.
You are my personal Hero!
Not to thread jack but do happen to have a backup of kernel.org?
Sent from my SCH-I800 using xda premium
Hey I sent you a email Oldmacnut. Sorry, didn't see you turned it off.
The zip you provided is broken I think. cwm says it's bad, and when i open with winrar it says unexpected end of archive.
Otherwise great work! I'm loving the support you've given verizon gtabs!
caldeio said:
Hey I sent you a email Oldmacnut. Sorry, didn't see you turned it off.
The zip you provided is broken I think. cwm says it's bad, and when i open with winrar it says unexpected end of archive.
Otherwise great work! I'm loving the support you've given verizon gtabs!
Click to expand...
Click to collapse
This os why I prefer hdimdall
Sent from my DROIDX using xda premium
I rooted my tab when it was on froyo, unrooted it when the gb update rolled out and never felt the need to root it again.
If you get cm7 on my tab, I personally promise a hefty donation from me!
I'm so thankful us Sprint users have you in our corner. I have an evo 3d and there are more roms to flash that I don't know what to do with myself and cm7 is on the horizon for that phone also. Sprint didn't get as much love for our tabs dev wise (I'm not *****ing, god knows I'm not capable of doing anything but flashing) over here.
If there's anything I can do to help shoot me a pm.
Sent from my unrooted Galaxy Tab.
Kudos! I hope this will get you closer to the Dev title!
C.
We're cheering for you man
Updated OP with more info, im sure there will be more today, and hopefully, i am crossing my fingers, a move to Beta and stability
Links updated?
Sent from my SPH-D700 using XDA App
Dev update, last one for the night.
Exciting news! Gonna be hard for me to stay focused at work today.
Sent from my SPH-D700 using XDA App
Way to go omc! Rest is a good thing.give the testers some time to run the gauntlet and have a nice organized list rather than a piece by piece fix to drive you crazy
Sent from my SCH-I510 using Tapatalk
update
.
seeing how you work, i could say "this guy is awesome"
though i haven't tried this rom...im on overcome..
Hope the dog is OK.
Sent from my SCH-I510 using xda premium
How's the dog?
Sent from my SPH-P100 using XDA App
First of all I want to make some things clear:
This is my own custom build I made with the help of this great tutorial: http://forum.xda-developers.com/showthread.php?t=775505
This has nothing to do with the offical nightly build from Cyanogen and his team.
I won't provide any support for this. If you want to flash this you should know what you do. Don't ask me anything like "How do I flash this?".
This could be even more unstable then the official nightly build since I add commits that are not merged. It's a great feature preview, but I can't guarantee anything. I can't tell you if the features you see here will make it into any official build.
What is it?
Its a custom build of the latest Cyanogen sources spiced up with some not (yet?) merged patches.
I don't know how often I will make new builds, it depends if I find new things I want to try. If there are no new commits that interest me I won't make a new build.
I will only upload builds that work for me. So the basic stuff should work for everyone, if it doesn't try to wipe before flashing. If it still doesn't work use the official nightly/RC/stable/whatever... (Thats the point with "I won't provide any support").
Difference to the official CM nightly
Download
MD5
I made something like this already for the Nexus One and many people liked it.
And since we don't get official nightlys since a long time already I thougt I start making my own nightlys again.
02/10/2012: new build, added latest commits from cm + cherry picked commits (again with AROMA Installer to choose WiFi calling)
02/04/2012: same build but with AROMA Installer. You can choose if you want to have WiFi calling or not before flashing the ROM.
02/01/2012: new build, added latest commits from cm + cherry picked commits
Thanks dude, good work.
I compiled my own CM7 Rom, but not sure how to apply those unapproved changes from the review platform, would u give me a hint ?
pentie said:
Thanks dude, good work.
I compiled my own CM7 Rom, but not sure how to apply those unapproved changes from the review platform, would u give me a hint ?
Click to expand...
Click to collapse
You need to cherry pick them
http://wiki.koha-community.org/wiki/Using_Git_Cherry_Pick
Why is anybody still screwing around with Android 2.3? This line is finished/dead/obsolete. Let it go already.
dhkr234 said:
Why is anybody still screwing around with Android 2.3? This line is finished/dead/obsolete. Let it go already.
Click to expand...
Click to collapse
How is it dead? 2.3 is what our phones can run most efficiently with speed and smoothness, 4.0 is still choppy and major graphical glitches. Not everyone wants an unstable rom which will not be at it's optimum until a while longer.
On the other hand, I will be trying this out and thank you for putting in your time and effort to bring us another rom to choose from
I noticed no wifi calling....
I noticed in your docs that wifi calling is not included, any chance of getting this added back in?
dhkr234 said:
Why is anybody still screwing around with Android 2.3? This line is finished/dead/obsolete. Let it go already.
Click to expand...
Click to collapse
Since ICS ROMs don't have camera fully working I wouldn't consider 2.3 dead. Many people including myself require a fully functional camera.
With that said I actually couldn't get camera and gallery to work on this ROM. I flashed it on top of stable CM 7.1.0 wiping only cache and dalvik.
I'm not going to do a full wipe at this point, neither am I looking for support but thought I would mention it.
dhkr234 said:
Why is anybody still screwing around with Android 2.3? This line is finished/dead/obsolete. Let it go already.
Click to expand...
Click to collapse
The Cyanogenmod team is still going to release CM 7.2. So they're also still "screwing" around with it.
dhkr234 said:
Why is anybody still screwing around with Android 2.3? This line is finished/dead/obsolete. Let it go already.
Click to expand...
Click to collapse
What???
You say that the version which works best on our phone is dead?
You mean 4.0 which brings us graphical glitches, no fully functional camera, bluetooth issues ... is better?
Lets talk about this in half a year again, but for now Gingerbread is the most stable and best performing version for our phones.
bradley_e_smith said:
I noticed in your docs that wifi calling is not included, any chance of getting this added back in?
Click to expand...
Click to collapse
Maybe I'll make an additional zip for wifi calling, I won't include it in the rom for sure since I can't use it.
Just a heads up...for some reason removing the wifi calling files breaks my APN connection with AT&T. Makes no sense on the surface. Put back both the apks and the libs and I've got signal again.
sisterchick said:
Just a heads up...for some reason removing the wifi calling files breaks my APN connection with AT&T. Makes no sense on the surface. Put back both the apks and the libs and I've got signal again.
Click to expand...
Click to collapse
Did you change something in the build.prop too?
Everthing works fine here, making calls, data connection...
Sent from my HTC Vision using Tapatalk
g4rb4g3 said:
Did you change something in the build.prop too?
Everthing works fine here, making calls, data connection...
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
No, I didn't touch build.prop. I thought I may try it again tonight, removing the apks and libs one at a time to see what breaks the connection with AT&T.
sisterchick said:
No, I didn't touch build.prop. I thought I may try it again tonight, removing the apks and libs one at a time to see what breaks the connection with AT&T.
Click to expand...
Click to collapse
Weird, without changing the rilpath in build.prop the libs you pushed won't get loaded...
I'm curious which file is making you connection work again, please tell me when you found it out. Thanks!
Sent from my HTC Vision using Tapatalk
erichung_13 said:
How is it dead? 2.3 is what our phones can run most efficiently with speed and smoothness, 4.0 is still choppy and major graphical glitches. Not everyone wants an unstable rom which will not be at it's optimum until a while longer.
On the other hand, I will be trying this out and thank you for putting in your time and effort to bring us another rom to choose from
Click to expand...
Click to collapse
Agreed 2.3 is the most stable, ICS has a long way to go.
tarroyo said:
Agreed 2.3 is the most stable, ICS has a long way to go.
Click to expand...
Click to collapse
The key word you've used is STABLE.
No need to keep dicking around with what already exists. If you want to use it, fine. But there's nothing left worth adding to it, and DEVELOPERS NEEDED ON 4.0!!!
dhkr234 said:
The key word you've used is STABLE.
No need to keep dicking around with what already exists. If you want to use it, fine. But there's nothing left worth adding to it, and DEVELOPERS NEEDED ON 4.0!!!
Click to expand...
Click to collapse
Your bridge is waiting for you.
dhkr234 said:
The key word you've used is STABLE.
No need to keep dicking around with what already exists. If you want to use it, fine. But there's nothing left worth adding to it, and DEVELOPERS NEEDED ON 4.0!!!
Click to expand...
Click to collapse
Whoa bro, what's up with you? Any kind of development for our phone should be appreciated. ics is on its way. We already have 3 dev teams working on it. If g4rbag3 wants to work on something else and you don't like it, quit dicking around in his thread.
Since I saw some nice commits got merged I made an update.
g4rb4g3 said:
Since I saw some nice commits got merged I made an update.
Click to expand...
Click to collapse
This nigga knows !
#IgnoreTheHaters
Hi guys. Has anyone else tested this rom yet? Been running it for a little over a week and except for the known issues with JB it is really solid. There hasn't been anything in the thread since 8/5 and I anted to make sure it's still being developed.
enigma2u2 said:
Hi guys. Has anyone else tested this rom yet? Been running it for a little over a week and except for the known issues with JB it is really solid. There hasn't been anything in the thread since 8/5 and I anted to make sure it's still being developed.
Click to expand...
Click to collapse
I didnt think no nobody was using it. To be honest I had stop using it myself. Yes development will still be going on. The next update is going to be built from source. I tired to build it Saturday I believe but something was wrong with google's servers. So I will start on it today and see if I get any luck. :fingers-crossed: And also downgrade my Ubuntu from 12.04 to 11.10 that should fix some problems.
StaticMaal said:
I didnt think no nobody was using it. To be honest I had stop using it myself. Yes development will still be going on. The next update is going to be built from source. I tired to build it Saturday I believe but something was wrong with google's servers. So I will start on it today and see if I get any luck. :fingers-crossed: And also downgrade my Ubuntu from 12.04 to 11.10 that should fix some problems.
Click to expand...
Click to collapse
I'm loving your rom. It's my daily driver even without being fully functional. I've found that I don't have to take pictures or watch netflix to enjoy my EVO. I was on Reloaded prior to trying this one but could never get it to be totally stable. Sure it was user error but I haven't had 1 freeze or reboot with this one. Let me know if you need me to test something as I will be running this at least until reloaded .500 releases. I can still see this as a daily once it's complete.
enigma2u2 said:
I'm loving your rom. It's my daily driver even without being fully functional. I've found that I don't have to take pictures or watch netflix to enjoy my EVO. I was on Reloaded prior to trying this one but could never get it to be totally stable. Sure it was user error but I haven't had 1 freeze or reboot with this one. Let me know if you need me to test something as I will be running this at least until reloaded .500 releases. I can still see this as a daily once it's complete.
Click to expand...
Click to collapse
You don't like reloaded! wha wha what! You smoking crack!?!
Sent from my PC36100 using xda premium
Of course I like it I just never got mine too be totally stable. It would freeze on me often and I never took the time to figure out how to get a report using log cat so never had evidence of what was happening. Since I was pulling the battery to restart I didn't know if it would log something that happened prior to battery pull. Also could never get the widgets to survive a restart.
Crack.....no
Sent from my EVO using Tapatalk
First of all, I know I am in the general section when I should be posting in the thread of the current rom I am running. But the forum will not let me, it says I have an insufficient post count to post in a development section which is where thread is located. (I think this is a pretty stupid rule, especially when a person like me who lurks these forums and uses it to find roms to use, and when that lurker needs to find help they cannot post in the appropriate section ; end rant).
Anyway, onto the boot loop problem. My current phone setup is : ParanoidAndroid 1.9.7 for the ROM and Trinity kerenl with 1344Ghz cpu clock and 304Ghz gpu clock.
What is happening is a boot loop at the Google screen. The first time this happened, my on screen navigation keys disappeared and when I tried to reboot my phone it boot looped. To fix it i had to do a clean install (I still have access to recovery when this happens). That was about 4 or 5 days ago, and I was fine up until now. This time the navigation keys didn't disappear, it was just a normal reboot that I did because when i plugged my phone in for the night it didn't display that it was charging, this is a normal thing for me and all it takes is a reboot and it will display charging status. Except this time when I went to reboot it, it boot looped at the Google screen again. I heard that a dirty flash of the rom may help, but I am not sure about this, and I don't want to screw my phone up anymore than it is, other than that I am pretty stuck as far what to do to fix the problem goes.
If more information is needed or if my explanation is unclear just post.
Any help is appreciated. Thanks in advance.
crashngo said:
First of all, I know I am in the general section when I should be posting in the thread of the current rom I am running. But the forum will not let me, it says I have an insufficient post count to post in a development section which is where thread is located. (I think this is a pretty stupid rule, especially when a person like me who lurks these forums and uses it to find roms to use, and when that lurker needs to find help they cannot post in the appropriate section ; end rant).
Anyway, onto the boot loop problem. My current phone setup is : ParanoidAndroid 1.9.7 for the ROM and Trinity kerenl with 1344Ghz cpu clock and 304Ghz gpu clock.
What is happening is a boot loop at the Google screen. The first time this happened, my on screen navigation keys disappeared and when I tried to reboot my phone it boot looped. To fix it i had to do a clean install (I still have access to recovery when this happens). That was about 4 or 5 days ago, and I was fine up until now. This time the navigation keys didn't disappear, it was just a normal reboot that I did because when i plugged my phone in for the night it didn't display that it was charging, this is a normal thing for me and all it takes is a reboot and it will display charging status. Except this time when I went to reboot it, it boot looped at the Google screen again. I heard that a dirty flash of the rom may help, but I am not sure about this, and I don't want to screw my phone up anymore than it is, other than that I am pretty stuck as far what to do to fix the problem goes.
If more information is needed or if my explanation is unclear just post.
Any help is appreciated. Thanks in advance.
Click to expand...
Click to collapse
Why don't you try with 1.99 version? Also theres a fix for 1.9.7 did you installed it?
EDIT:
Also what GN are you using GSM?
Rotary Heart said:
Why don't you try with 1.99 version? Also theres a fix for 1.9.7 did you installed it?
EDIT:
Also what GN are you using GSM?
Click to expand...
Click to collapse
I was actually downloading 1.99 as I was typing that, and I was not aware of a fix for 1.97. What was the fix exactly? If it was for a boot loop problem I will feel like a total moron and sorry for wasting everyone's time.
Its CDMA.
crashngo said:
I was actually downloading 1.99 as I was typing that, and I was not aware of a fix for 1.97. What was the fix exactly? If it was for a boot loop problem I will feel like a total moron and sorry for wasting everyone's time.
Its CDMA.
Click to expand...
Click to collapse
Well I have GSM so I don't know if they are keeping it up the same but try the 1.99 with wipe and everything, report back when you are done. I don't remember what the fix do, but there is one.
Rotary Heart said:
Well I have GSM so I don't know if they are keeping it up the same but try the 1.99 with wipe and everything, report back when you are done. I don't remember what the fix do, but there is one.
Click to expand...
Click to collapse
There is a 1.99 for CDMA so I am going to flash that.
Rotary Heart said:
Well I have GSM so I don't know if they are keeping it up the same but try the 1.99 with wipe and everything, report back when you are done. I don't remember what the fix do, but there is one.
Click to expand...
Click to collapse
Well I flashed 1.99, only time will tell how it does.
Also I noticed your screen name, do you drive a rx-7 or rx-8?
crashngo said:
Well I flashed 1.99, only time will tell how it does.
Also I noticed your screen name, do you drive a rx-7 or rx-8?
Click to expand...
Click to collapse
I have had 5 RX-7 and I'm only 21... and more to come
Rotary Heart said:
I have had 5 RX-7 and I'm only 21... and more to come
Click to expand...
Click to collapse
Holy crap....lol
Im looking into getting a gen 1 RX- 8 just alittle worried about the renesis motors.
crashngo said:
Holy crap....lol
Im looking into getting a gen 1 RX- 8 just alittle worried about the renesis motors.
Click to expand...
Click to collapse
Worried why?
Rotary Heart said:
Worried why?
Click to expand...
Click to collapse
I've heard they can be very finicky and if not taken care of properly they'll have problems.
crashngo said:
I've heard they can be very finicky and if not taken care of properly they'll have problems.
Click to expand...
Click to collapse
Well same with any other engine, they need some care, but if you do it right (its not hard at all) you can have a sexy Daily Driver for a lot of years :highfive:
Rotary Heart said:
Well same with any other engine, they need some care, but if you do it right (its not hard at all) you can have a sexy Daily Driver for a lot of years :highfive:
Click to expand...
Click to collapse
Very true, and thats what I am hoping for.
crashngo said:
Very true, and thats what I am hoping for.
Click to expand...
Click to collapse
Remember to report back if you have any issue. Also you should try to post in the developers section of Paranoid Android now that you can
Good Luck with both the car and the phone :good:
Rotary Heart said:
Remember to report back if you have any issue. Also you should try to post in the developers section of Paranoid Android now that you can
Good Luck with both the car and the phone :good:
Click to expand...
Click to collapse
Will do, and thanks.
Any chance you found a resolution. I can't get mine to work either.
captnawesem said:
Any chance you found a resolution. I can't get mine to work either.
Click to expand...
Click to collapse
What version and kernel are you using?
Okay so there are two multi-boot modifications flowing around XDA for a ton of various devices.. Has anyone ever considered porting one to the robin? lately with all these rock solid Roms it doesn't seem like too bad of an idea and I truly wish I had the experience to do it myself.
https://github.com/chenxiaolong/DualBootPatcher/
and
https://github.com/Tasssadar/multirom
and
https://github.com/efidroid/
Oh hell yes! I'd like to see this!
Desperately waiting for it!
Sounds cool, I can have Omni and XOSP at the same time ;P
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Porting-a-new-device
If you ask me, the lack of the need of the kexec-hardboot patch makes this project superior to multirom
Alexandroid99 said:
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Porting-a-new-device
If you ask me, the lack of the need of the kexec-hardboot patch makes this project superior to multirom
Click to expand...
Click to collapse
I'm taking a look at it and i'm gonna mess around with it and hopefully make an attempt to port it.. Hope all goes well
AnierinB said:
I'm taking a look at it and i'm gonna mess around with it and hopefully make an attempt to port it.. Hope all goes well
Click to expand...
Click to collapse
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Alexandroid99 said:
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Click to expand...
Click to collapse
Yeah but unfortunately for me repo is giving me a ton of problems and i've got to get to work. if someone else wants to try this, be my guest.
AnierinB said:
Yeah but unfortunately for me repo is giving me a ton of problems and i've got to get to work. if someone else wants to try this, be my guest.
Click to expand...
Click to collapse
I'm already syncing it. Someone got it to work partially on the Nexus 5X, which is the same arch. So fingers crossed...
Alexandroid99 said:
I'm already syncing it. Someone got it to work partially on the Nexus 5X, which is the same arch. So fingers crossed...
Click to expand...
Click to collapse
Let me know how it goes man :highfive:
Alexandroid99 said:
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Click to expand...
Click to collapse
No dice. Tried to compile lk using msm8994 (SD810- same workaround as 5x) and was able to fastboot boot a nouefi lk.img but but once booted there was no device showing up in fastboot devices which unfortunately is key to the next step
A lot of Devs are getting into issues assuming that this device is similar to the 5X. No. It isn't. This device's implementation is completely different. Take a look at the two sources and you'll see it. NextBit's calls to device and storage are also different. Boot patches won't work the same way. The OmniROM Dev was the first to learn this which is why it took a lot of time. Also Robin doesn't seem to respond to slot switching though it has it. I may be wrong.
valhallen.282 said:
A lot of Devs are getting into issues assuming that this device is similar to the 5X. No. It isn't. This device's implementation is completely different. Take a look at the two sources and you'll see it. NextBit's calls to device and storage are also different. Boot patches won't work the same way. The OmniROM Dev was the first to learn this which is why it took a lot of time. Also Robin doesn't seem to respond to slot switching though it has it. I may be wrong.
Click to expand...
Click to collapse
I got lk to boot using the same lk_base as the 5x so there are a few thing in common because the aboot dump showed the same value. anyways I made some progress: Display to show, finalize_device to execute and was able to build uefi.img and boot it. upon booting uefi the kernel panics and reboots so I have to to figure that out before proceeding to the checklist.
valhallen.282 said:
A lot of Devs are getting into issues assuming that this device is similar to the 5X. No. It isn't. This device's implementation is completely different. Take a look at the two sources and you'll see it. NextBit's calls to device and storage are also different. Boot patches won't work the same way. The OmniROM Dev was the first to learn this which is why it took a lot of time. Also Robin doesn't seem to respond to slot switching though it has it. I may be wrong.
Click to expand...
Click to collapse
Alexandroid99 said:
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Click to expand...
Click to collapse
I've got it to boot and run for the most part but I'm not the most experienced at porting and there are a few things left to do like configuring the fstab.multiboot correctly which is key to multi booting roms and installing the ota through efidroid app via github sever
AnierinB said:
So I've got efi-droid ported and working for the most part. I'm not the most experienced at porting and there are a few things left to do like testing multiboot roms and configuring a local ota sever to do so..
I'm making this post so that I can hand off my findings, config.ini, and my lk_inc.make to someone who has more experience/ someone who can get this done and wants to test multiboot and see if it's a go. Think you can do so and become the maintainer for this project?
Click to expand...
Click to collapse
I wish I was smart enough to do that. I can read code. I can test. Cannot write to save my life. Sorry. That's my truth.
valhallen.282 said:
I wish I was smart enough to do that. I can read code. I can test. Cannot write to save my life. Sorry. That's my truth.
Click to expand...
Click to collapse
As soon as I get these local ota server problems figured out and are able to actually test dual booting a rom I'll pm you with some goodies:good:
It's pretty easy to build yourself after you figure out what variables the lk.mk and config.ini need. Although I have been doing this for 3 days now with many trial and error. Pretty shocked it's even working as good as it is right now because there's been a lot of known issues with 64bit socs
delete
I'm gonna have to put this project behind me... I lack some knowledge on a few areas of the porting process and to configure it correctly is possible but I, myself can not do it. If a developer has the device, and wants to try porting/configuring it then go for it. The main thing is that we are able to get lk, uefi to boot and display screen (properly) so fixing the other issues like fstab.multiboot table should be easy for someone more experienced. At least theres hope with this modification. Sorry folks, I'll stick to my boot logos for now haha.
AnierinB said:
@ValHallen can you download the efi manager application off the play store and tell me what device it gives you an error for? then after doing so can you edit your build prop and add this line: efidroid.server_url=https://raw.githubusercontent.com/anierinbliss/efidroid_ota/master
then delete the app, reboot your phone and reinstall it.. Does it still fail?
Click to expand...
Click to collapse
I think you tagged the wrong person. But I'll try. In a short while.
It's probably best to put all thaz work out in the open including github repos and a separate thread so someone who's capable might stumble upon it and pick up qhere you left off.