Related
Full credit goes to Ssserpentine, SpaceMoose, and OldMacnut for their work on their united efforts to port Honeycomb to our tablets! It seems they are no longer working on it so I decided to create this thread and see what we all could to do together to improve what they have given us!
The point of this thread is to find ways to gather anyone with knowledge on developing, even if its just the "lowly 7-Zippers" like me, to see how we can remove minor bugs and small issues from the ROM. I know Oldmacnut was going to pick it up, but he has a lot on his plate right now and he has been in pain and is more interested in finishing the CM7 Port instead. I respect his decision, but so many people want honeycomb working on our tabs. So I am turning to the dev community here to see if we can group together and fix things in this rom together. If we cant solve the major bugs, lets address all the little things, cuz the little things add up.
Spacemoose made a list of suggestions from users earlier on how to solve minor issues, and little workarounds, but I would like to see if there is a way to roll up those fixes into one full updated ROM flashable through a zip/odin/heimdall file, and see if we can come up with more. You can see this post here, but I have added them to the second post as well in a more organized form.
Some Useful Links as Well:
SpaceMoose's Github
6-19-11 Apps Confirmed Working on [CDMA] / [GSM] Honeycomb Alpha 2.5
Currently Known Bugs:
CDMA
A) Red Border Around Screen at Random Times
B) Constant Gallery Force Close
C) Stock Launcher hangs for many seconds at a time randomly
D) SD Card Does Not Mount
E) Youtube app does not work
F) Orientation Sensor is not functional
G) Honeycomb thinks Device Keyboard is enabled by default
H) When pressing Quick Settings, an image that is semi transparent that is supposed to cover the entire screen isnt scaled properly
I) HQ Youtube does not work (LQ does on the mobile site)
J) Quick Settings Shortcut on Bottom Right Side (Wi-Fi Toggle, Brightness Slider, etc) appears for a second but disappears afterwards.
K) Flash Player is not Fully Functional
GSM - Please Submit or confirm if the above bugs are the same and/or you have different ones!
Red - Signifies an issue that is unaddressed or has not been solved yet.
Orange - Signifies a Temporary Fix or Workaround is mentioned in the post I linked to.
Blue - Will signify a temporary fix or a work around that we have been able to include in a flashable file
Green - Will signify a bug that has been completely fixed in a flashable file.
------------------------------------------
Lets put our minds together and see what we can do guys! Btw this was inspired by Rodderik's thread [SPRINT][CDMA]Galaxy Tab (SPH-P100) Mega Development Starter Thread (CWM, EF17 TAR), so if youre interested in this, you might like his thread too!
Current Workarounds/Temporary Fixes:
Letters correspond to the bugs listed in the OP.
A)
Ssserpentine:
1) Open up Dev Tools
2) Go to Development Settings
3) StrictMode Visual Indicator - turn it off
4) back out of app and now open it again.
5) If this doesn't get rid of MOST of the red borders, REBOOT and open app again.
Click to expand...
Click to collapse
B)
anfalas:
"Get Gallery3D to play nice by going into settings, applications then 'Clear Data' - works great, can change wallpaper etc. Only downside is it has to be done each reboot....."
Click to expand...
Click to collapse
C)
Ssserpentine:
“WANT IMPROVED UI, LESS RED BORDERS, LESS FC'S AND SCROLLING AND SOFT KEYS THAT PLAY NICER? Try adw launcher. for some reason just having it installed helps just as much as using it.”
Click to expand...
Click to collapse
D)
mattman83:
"to mount UMS if you have no external SD then use the below line. Same changes as above... echo /dev/block/mmcblk0p1 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file"
Click to expand...
Click to collapse
or
corodius:
"if you have an external sd, by extending the commands to: su mount -t vfat /dev/block/mmcblk0p1 /mnt/sdcard/ mount -t vfat /dev/block/mmcblk1p1 /mnt/sdcard/external_sd/ This will mount the cards the way they are originally mounted in the samsung/overcome roms."
Click to expand...
Click to collapse
E)
Use m.youtube.com to play LQ videos
Click to expand...
Click to collapse
F)
ztag100:
"If you download barcontrol from the market, you can set it so that a notification links to the rotation app, thus when the notification is clicked it will change the orientation."
Click to expand...
Click to collapse
G)
"one way to load keyboards On the language/keyboard settings page, turn physical keyboard to "no" or "off" or something like that. Now when on a text field, you should see a small keyboard tray in bottom right corner.."
Click to expand...
Click to collapse
H) ---
I) ---
J) ---
K) ---
----------------------------
Submit a New Bug or Fix:
Please submit bugs using the color coded system I explained in the OP. If you are submitting information on solving a bug please address the bug by the corresponding letter so that we can stay organized and know what youre talking about. If you have a new bug please check the OP to make sure I havent listed it, then post it on here and dont worry about the letter, I will alphabetize them. Of course I will credit you in the OP for any fixes or workarounds you may find! Good luck to us all!
Reserved as well!
Yes, please
I would really love a Honeycomb ROM for the Galaxy Tab. There are many reasons why I want to put Honeycomb onto the original Galaxy Tab.
Just see the difference for yourself: Blank space, single pane, one-category-at-a-time menus in Gingerbread
VS.
Less blank space, concise, dual pane interfaces in Honeycomb.
Gingerbread apps are just designed for smaller smartphone screens, so they look too big and spaced-out on the 7-inch Galaxy Tab for my taste. I would really love to see some tablet-optimized apps on the Galaxy Tab!
-------------------------
And yes, I respect the developers and appreciate them so much for the time they put into making custom roms a reality for us!
Please make the thread for GSM also.
TheATHEiST said:
Please make the thread for GSM also.
Click to expand...
Click to collapse
Are the bugs the same? Or are there others that I havent mentioned? I will try to make a section for both tabs if theres different bugs in each one.
Why no mention of ssserpentine?
In op or thread tittle?
He worked on the GSM version.
Moose did the major part of the port and the cdma version.
That other person stumbled, or so he claims, on a audio fix. Never saw a release of this apparent audio fix.
Wonder how many donations he got on open thread with no release posted.
Hmm.
Makes ya wonder why that thread is even there.
Dole out the credits properly.
Just know it needed to be said, and go ahead and get mad. Truth hurts.
alot of angry responces coming, maybe, but dare ya to point out a single lie in this post. Even an exaggeration.
Moose did hc for MONTHS and noone offered any valid help, except ssserpentine, why do you think anyone is gonna get off their but now?
Why don't you, punkrock?
Cause I know how utterly hopeless this task is.
Why don't you all just wait for the leak of the next os?
That so much closer than some random Joe, or Joe's on xda getting hc ported at this point .
is the dead horse braised yet?
Still, hope is eternal, I suppose
PunkRock said:
Why no mention of ssserpentine?
In op or thread tittle?
He worked on the GSM version.
Moose did the major part of the port and the cdma version.
That other person stumbled, or so he claims, on a audio fix. Never saw a release of this apparent audio fix.
Wonder how many donations he got on open thread with no release posted.
Hmm.
Makes ya wonder why that thread is even there.
Dole out the credits properly.
Just know it needed to be said, and go ahead and get mad. Truth hurts.
alot of angry responces coming, maybe, but dare ya to point out a single lie in this post. Even an exaggeration.
Moose did hc for MONTHS and noone offered any valid help, except ssserpentine, why do you think anyone is gonna get off their but now?
Why don't you, punkrock?
Cause I know how utterly hopeless this task is.
Why don't you all just wait for the leak of the next os?
That so much closer than some random Joe, or Joe's on xda getting hc ported at this point .
is the dead horse braised yet?
Click to expand...
Click to collapse
Easy man, in my frenzy of trying to organize the thread, I forgot to credit Ssserpentine in the OP, youre right he did contribute a lot, no need to be rash, I will update it right now.
EDIT: btw oldmacnut did make an audio fix, im running his rom right now, I downloaded it when he had it posted before he took it down, and Im sure some of the bugs I mentioned are fixable on the rom level rather than through adb. My goal wasnt to debug the rom completely, it was to incorporate all the existing bug fixes and workarounds into one rom, while possibly solving others. Also the GSM devs are aplenty here, while we barely have any CDMA, Im sure we have enough talent to make it better than what it is. It might not be flawless, but Im sure we can squeeze more functionality out of it.
Its weird,
Honeycomb is more or less froyo based, obviously as we had hc long before gb, so at the time when I started getting into this whole dev thing hc/froyo seemed just different to me.
But after working on the abortion called gingerbread, and working onbthe kernel stuff, froyo to me, is starting to look like a much more viable and dev friendly option.
Alot if the work Dan did in hc was from scratch, or from the sdk, etc. The audio fix I did was from both.
The big issue on getting hc up and going into a usuable rom is source, we really really need that source for hc. Otherwise, its going to be a long drawn out road of trial and error building with alot of these issues never really getting fixed.
Truth is,
No device with our hardware exists with hc, so no drivers that we need.
We need Google to release the hc source.
I liked hc on my tab just like y'all, but.......I know its just a novel weekend fun toy till we get better resources.
Sent from my SCH-I800 using xda premium
oldmacnut said:
Its weird,
Honeycomb is more or less froyo based, obviously as we had hc long before gb, so at the time when I started getting into this whole dev thing hc/froyo seemed just different to me.
But after working on the abortion called gingerbread, and working onbthe kernel stuff, froyo to me, is starting to look like a much more viable and dev friendly option.
Alot if the work Dan did in hc was from scratch, or from the sdk, etc. The audio fix I did was from both.
The big issue on getting hc up and going into a usuable rom is source, we really really need that source for hc. Otherwise, its going to be a long drawn out road of trial and error building with alot of these issues never really getting fixed.
Truth is,
No device with our hardware exists with hc, so no drivers that we need.
We need Google to release the hc source.
I liked hc on my tab just like y'all, but.......I know its just a novel weekend fun toy till we get better resources.
Sent from my SCH-I800 using xda premium
Click to expand...
Click to collapse
Yeah I know, the lack of source sucks along with the fact we dont have drivers. I dont think we'll have everything working anytime soon at all, if ever even, but I think some of the minor annoyances like the disappearing quick settings toggle, sdcard mounting issues, and graphical errors can be solved without that kind of stuff. Me personally, Id just like HQ Video Playback and 3D Graphics working a hundred percent along with orientation, but as you said no drivers so idk how easy that'd be. Still, Im sure we could solve some of these minor issues. I keep browsing over the Nook Color Forums trying to find hints to solving some of these things
GSM Tab here I'll flash the old 2.5 alpha release and confirm these bugs, see what else I can do.
Sent from my GT-P1000 using xda premium
BulletproofIdeal said:
GSM Tab here I'll flash the old 2.5 alpha release and confirm these bugs, see what else I can do.
Sent from my GT-P1000 using xda premium
Click to expand...
Click to collapse
Nice to see something happening here. I love my Tab but would like some advancements in OS to address specific issues. I am very new to the dev side of the Android OS but would like to get involved.
--Mike
What blows my mind is that they have created an almost perfect HC port for the $150.00 walmart sold viewsonic g-tablet by means of the flashback roms so why is it so hard to get HC working on our tabs? And why can't someone just dump the Rom from the gtab10.1 and use that as a starting point?
On a different note, the alpha 2.5 HC Rom for gsm, the sd cards will not mount no matter what, I've tried The terminal and the mount instructions many times all I am able to do is get the tab to recognize my external sd as the internal sd, and if you try to go to settings applications and clear data for the gallery you get a force close as soon as you tap manage applications
Sent From Githrog's Tab
Ok done some immediate testing on my GSM Tab for some of the known issues
A) Red Border Around Screen at Random Times
Confirmed
Solution: is the same as the CDMA
B) Constant Gallery Force Close
Confirmed
Solution: Cannot be fixed through Setting, crashes as soon as you try to Manage Applications
C) Stock Launcher hangs for many seconds at a time randomly
Not really was slow on boot but no major problems
D) SD Card Does Not Mount
Confirmed
Solution: Haven't tested fix yet
E) Youtube app does not work
Confirmed
Solution: Confirmed
F) Orientation Sensor is not functional
Confirmed
Solution: "Rotating Screen" flips screen incorrectly so that capacitive buttons are on the top of the device
G) Honeycomb thinks Device Keyboard is enabled by default
Confirmed
Solution: Must be set on each boot
H) When pressing Quick Settings, an image that is semi transparent that is supposed to cover the entire screen isnt scaled properly
Confirmed
I) HQ Youtube does not work (LQ does on the mobile site)
Confirmed
J) Quick Settings Shortcut on Bottom Right Side (Wi-Fi Toggle, Brightness Slider, etc) appears for a second but disappears afterwards.
The widget that display battery level, time, etc stays active however no settings are located underneath it. While this menu is expanded a press on the bottom bar will cause the settings to briefly appear but then the whole menu will close
K) Flash Player is not Fully Functional
Not tested
"New" GSM bugs
1. Wi-fi settings are not saved on restart
2. Manage Applications and Running Services menu causes force close of settings
3. Small thing but Tab's first start had language set to Spanish (Not sure if it was spanish but it certainly was not English)
And as always 3G does not work (tried APN settings but it wouldn't let me save)
Alright I'm back to MIUI until I can find some more time on my hands
---------- Post added at 02:51 PM ---------- Previous post was at 02:31 PM ----------
Githrog said:
What blows my mind is that they have created an almost perfect HC port for the $150.00 walmart sold viewsonic g-tablet by means of the flashback roms so why is it so hard to get HC working on our tabs? And why can't someone just dump the Rom from the gtab10.1 and use that as a starting point?
Click to expand...
Click to collapse
If it were that simple I'm sure someone would have thought of that To be honest I think the problem is that the Tab is an extremely fractured device; it was really the first Android tablet to directly compete with the iPad, so it was spread as wide as possible. That's great for Samsung who got a pretty large base of customer but sucks for devs because the GSM and CDMA are 2 very different devices not to mention the P-1000N. When I got my Tab last month the first thing I noticed in this forum was the fragmentation between the different versions of Tabs. More profoundly this means that the developers are split apart, usually when one dev makes a break through everyone else can take advantage of it (i.e. the amazing Voodoo Sound/Color hacks) but not here. I feel like everyone is by themselves and I truly feel bad for the developers because they must make their own breakthroughs on top of dealing with complaints from Tab users with other versions that they want this awesome thing on their Tab. As if its no big deal to go and buy a $450 device to develop something as a hobby and then release it for free for people on the internet after already buying nearly the exact same device.
Sadly I think the Tab is a perfect storm working against modifying it in any ground breaking ways. Don't get me wrong I love my Tab and will try to help getting Honeycomb running but I almost feel like it would just be easier to wait for Ice Cream Sandwhich. /rant
Guys, there is no reason to develop honeycomb, it is inposible to make fully functional honeycomb rom, wait a month or less for ICS, read this (quote from android police posted today):
Honeycomb is closed source. Nobody can make a tablet without Google's blessing. The reason given is that Honeycomb was rushed out the door, and the code isn't good enough for an open source release. They're right you know, setting the emulator to anything smaller than a tablet will result in about a million force closes. Honeycomb just isn't as supportive of hardware as Gingerbread was. To save developers the headache of supporting a platform that wasn't ready, Android's openness got shelved.
Luckily this is going to change. The big cheese said so himself on the Official Android Developers blog, "This temporary delay does not represent a change in strategy. We remain firmly committed to providing Android as an open source platform across many device types." Source code is coming back. This will make the modding community's life much easier. Cyanogenmod 8 (I got excited just typing that) and Ice Cream Sandwich will be able to get hacked onto just about anything.
Click to expand...
Click to collapse
CROrION said:
Guys, there is no reason to develop honeycomb, it is inposible to make fully functional honeycomb rom, wait a month or less for ICS, read this (quote from android police posted today):
Click to expand...
Click to collapse
I just wanted an excuse to try out Honeycomb
BulletproofIdeal said:
Ok done some immediate testing on my GSM Tab for some of the known issues
A) Red Border Around Screen at Random Times
Confirmed
Solution: is the same as the CDMA
B) Constant Gallery Force Close
Confirmed
Solution: Cannot be fixed through Setting, crashes as soon as you try to Manage Applications
C) Stock Launcher hangs for many seconds at a time randomly
Not really was slow on boot but no major problems
D) SD Card Does Not Mount
Confirmed
Solution: Haven't tested fix yet
E) Youtube app does not work
Confirmed
Solution: Confirmed
F) Orientation Sensor is not functional
Confirmed
Solution: "Rotating Screen" flips screen incorrectly so that capacitive buttons are on the top of the device
G) Honeycomb thinks Device Keyboard is enabled by default
Confirmed
Solution: Must be set on each boot
H) When pressing Quick Settings, an image that is semi transparent that is supposed to cover the entire screen isnt scaled properly
Confirmed
I) HQ Youtube does not work (LQ does on the mobile site)
Confirmed
J) Quick Settings Shortcut on Bottom Right Side (Wi-Fi Toggle, Brightness Slider, etc) appears for a second but disappears afterwards.
The widget that display battery level, time, etc stays active however no settings are located underneath it. While this menu is expanded a press on the bottom bar will cause the settings to briefly appear but then the whole menu will close
K) Flash Player is not Fully Functional
Not tested
"New" GSM bugs
1. Wi-fi settings are not saved on restart
2. Manage Applications and Running Services menu causes force close of settings
3. Small thing but Tab's first start had language set to Spanish (Not sure if it was spanish but it certainly was not English)
And as always 3G does not work (tried APN settings but it wouldn't let me save)
Alright I'm back to MIUI until I can find some more time on my hands
---------- Post added at 02:51 PM ---------- Previous post was at 02:31 PM ----------
If it were that simple I'm sure someone would have thought of that To be honest I think the problem is that the Tab is an extremely fractured device; it was really the first Android tablet to directly compete with the iPad, so it was spread as wide as possible. That's great for Samsung who got a pretty large base of customer but sucks for devs because the GSM and CDMA are 2 very different devices not to mention the P-1000N. When I got my Tab last month the first thing I noticed in this forum was the fragmentation between the different versions of Tabs. More profoundly this means that the developers are split apart, usually when one dev makes a break through everyone else can take advantage of it (i.e. the amazing Voodoo Sound/Color hacks) but not here. I feel like everyone is by themselves and I truly feel bad for the developers because they must make their own breakthroughs on top of dealing with complaints from Tab users with other versions that they want this awesome thing on their Tab. As if its no big deal to go and buy a $450 device to develop something as a hobby and then release it for free for people on the internet after already buying nearly the exact same device.
Sadly I think the Tab is a perfect storm working against modifying it in any ground breaking ways. Don't get me wrong I love my Tab and will try to help getting Honeycomb running but I almost feel like it would just be easier to wait for Ice Cream Sandwhich. /rant
Click to expand...
Click to collapse
Wow now that is the kinda posts i like seeing on here! I will try to update the OP tonight with this info! Thanks so much! Definitely echo your sentiments about the fractured and fragmented development we have going on here, it really sucks =/
Ive found out that replacing the existing Gallery with Gallery3D should fix the FC that keeps popping up.
I think Ive found a working Youtube App (in LQ).
Ive also found a hint towards solving the sdcard mounting issue. Its not the vold.fstab its something either in the framework or ramdisk within the kernel, according to the Nook Color Forums.
This thread is interesting: http://forum.xda-developers.com/showthread.php?t=1062626 , actually the entire nook color forum is interesting for finding fixes.
Also changing the dalvik_heapsize to a certain value is supposed to increase app compatibility. Before I update the OP with some of these things, I wanna do a little more testing and see what I can come up with.
Sorry to bother for help,
Sorry to bother you guys for help, but I've been trying to install Oldmacnut's updated of Spacemoose's CDMA Honeycomb (2.5.1) for hours now, with no success.
I used Rodderick's awesome stock rom/kernel and got into clockworkmod (using 4.0.1.5 or 3.0.0.0), installed the zip from there, then rebooted the phone, but I would either 1) be stuck at logo for 10+ minutes 2) see the Sprint startup video loop over and over again, or 3) get stuck on a turned on, but black screen.
How did you guys install Honeycomb on your CDMA tab? Am I doing something wrong? Should I use Spacemoose's 2.5 rom instead of Oldmacnut's?
EDIT: NEVER MIND, IT BOOTED INTO HONEYCOMB. I am in a foreign language, haha, I'm guessing Portuguese?
EDIT EDIT: Google Translate detects the language as Catalan. Haha!
iliveinabucket said:
EDIT EDIT: Google Translate detects the language as Catalan. Haha!
Click to expand...
Click to collapse
Hehe that happened to me as well
First Impressions and problems encountered
HOLY SHOOT THIS IS QUITE FAST!
Considering there is no graphics acceleration support, Honeycomb runs much faster than I anticipated. SD card support is fantastic, and so is hearing sound! (I love you OMC) The UI is awetastic and the standard web browser is blazing fast. Scrolling in web pages is faster on Honeycomb than on Gingerbread stock.
The jittery touch screen bug I have is still there, unfortunately. Damn bug drives me crazy sometimes. I'm sure somebody has this problem that many of us have but have not found a fix to: http://forum.xda-developers.com/showthread.php?t=970965
Basically, when I hold down my finger to scroll on white or light-color backgrounds, the screen shakes back and forth in a spastic, noticeable way, especially when I hold it in place. This happens on every single rom I've been on, froyo, GB, CM7, and now Honeycomb. Has anyone found a fix for that yet?
Anyways, I think all the known Honeycomb bugs are true to me too. Youtube force closes on me, GPS doesn't work, auto-orientation doesn't work. Strangely enough, Quick Settings doesn't work for me. Anyone encounter that?
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
This phone will never die
Synthetic.nightmare
I created an organzation on github alongside deadman and Awesome and rebased to the lovely aospX source code (for stability).
Tonight deadman worked along with me to try and get our script all set up to properly repo sync (+some other things) and after a bit more work, I have managed to get it to where we can sync using the proper b2g command ./config.sh as stated correctly in the readme. This is kind of a big deal, because before, I was just working around some of the scripts doing things the traditional android way lol. There's still parts that are needed to be rolled back and stuff and who knows what there might be broken even after we get all that worked out, but I thought that there might be some other devs around here that may be interested in helping bring this over to us and possibly others who want to keep track of this.
Links:
Click here to start preparing for/downloading the source to help us with development
Click here to see the b2gX organization and keep track of development
You can see more by clicking any of the member's githubs and checking out their activity.
Devs: PM Synthetic.nightmare if you want in. My team is always willing to collaborate with this who wish to contribute.
That's about all I can think of for now. Hopefully, we can bring you all some more good news soon.
Remember these links are here for you to keep track of development, so I don't wanna hear about no ETA's lol.
Click to expand...
Click to collapse
I have modified Synthetic-nightmare's ICS kernel, to hopefully support B2G here is the link
reserved
Mine
EDIT: Making this my reserve
Synthetic.Nightmare said:
This "build process" is just you syncing your repositories. There's still a mountain to climb once you get past this. It seems your manifest is off. When adjusting it look for things it says it cannot fetch. From there check to see if you got the repos and revisions and whatnot written out correctly in the xml in your manifest.
Sent from my MyTouch 4G using xda app-developers app
Click to expand...
Click to collapse
hmm i will look at that here is my manifest https://github.com/deadman96385/b2g-manifest/blob/master/default.xml
Very exciting! Thank You and good luck.
Fixed some errors
Ok i fixed all of the errors except the one in OP!
Holy crap this is awesome. I need to thank all the devs here for your hard work. This is just so amazing.
Sent from my Toasted Marshmallow using XDA
Looking good brother hopefully we will get this bad boy up and running soon...
Is this actual FirefoxOS? Or an Android rom of some sort? Didn't see much info in the OP lol
b4d455b345t said:
Is this actual FirefoxOS? Or an Android rom of some sort? Didn't see much info in the OP lol
Click to expand...
Click to collapse
Actual OS developed by Mozilla.
saranhai said:
Actual OS developed by Mozilla.
Click to expand...
Click to collapse
Ohhh shizzzz. :victory:
Our Glaciers would be able to rock 2 OSs (Android & Firefox) Can't wait.
A couple potential reasons for the repo sync error if you are still getting that:
First off.
Virtual or dual boot?
Which version of Ubuntu?
Laptop or Desktop?
Hard wired or wifi?
Potential Problems:
Unstable Wifi/ethernet driver- Recompile the driver
Wifi/router is going down- Keep the router awake?
MOST PROBABLE: Crappy repo file- Just delete the folder/make a new folder if you have space and make a fresh repo file and try to pull it down again.
---------- Post added at 11:42 PM ---------- Previous post was at 11:41 PM ----------
Also, how many processor cores do you have? do repo sync -j(#of processor cores + 1)
a pleasant update.
I have created an organzation on github alongside deadman and Awesome and rebased to the lovely aospX source code (for stability).
Tonight deadman worked along with me to try and get our script all set up to properly repo sync (+some other things) and after a bit more work, I have managed to get it to where we can sync using the proper b2g command ./config.sh as stated correctly in the readme. This is kind of a big deal, because before, I was just working around some of the scripts doing things the traditional android way lol. There's still parts that are needed to be rolled back and stuff and who knows what there might be broken even after we get all that worked out, but I thought that there might be some other devs around here that may be interested in helping bring this over to us and possibly others who want to keep track of this.
Links:
Click here to start preparing for/downloading the source to help us with development
Click here to see the b2gX organization and keep track of development
You can see more by clicking any of the member's githubs and checking out their activity.
Devs: PM me if you want in. My team is always willing to collaborate with this who wish to contribute.
That's about all I can think of for now. Hopefully, we can bring you all some more good news soon.
Remember these links are here for you to keep track of development, so I don't wanna hear about no ETA's lol.
THEindian said:
A couple potential reasons for the repo sync error if you are still getting that:
First off.
Virtual or dual boot?
Which version of Ubuntu?
Laptop or Desktop?
Hard wired or wifi?
Potential Problems:
Unstable Wifi/ethernet driver- Recompile the driver
Wifi/router is going down- Keep the router awake?
MOST PROBABLE: Crappy repo file- Just delete the folder/make a new folder if you have space and make a fresh repo file and try to pull it down again.
---------- Post added at 11:42 PM ---------- Previous post was at 11:41 PM ----------
Also, how many processor cores do you have? do repo sync -j(#of processor cores + 1)
Click to expand...
Click to collapse
I actualy have a Triboot,Ubuntu, Desktop,Hard Wired, i have deleted the folder am repulling down on to my extra hardrive. will edit when it finsh's.
Synthetic.Nightmare said:
a pleasant update.
I have created an organzation on github alongside deadman and Awesome and rebased to the lovely aospX source code (for stability).
Tonight deadman worked along with me to try and get our script all set up to properly repo sync (+some other things) and after a bit more work, I have managed to get it to where we can sync using the proper b2g command ./config.sh as stated correctly in the readme. This is kind of a big deal, because before, I was just working around some of the scripts doing things the traditional android way lol. There's still parts that are needed to be rolled back and stuff and who knows what there might be broken even after we get all that worked out, but I thought that there might be some other devs around here that may be interested in helping bring this over to us and possibly others who want to keep track of this.
Links:
Click here to start preparing for/downloading the source to help us with development
Click here to see the b2gX organization and keep track of development
You can see more by clicking any of the member's githubs and checking out their activity.
Devs: PM me if you want in. My team is always willing to collaborate with this who wish to contribute.
That's about all I can think of for now. Hopefully, we can bring you all some more good news soon.
Remember these links are here for you to keep track of development, so I don't wanna hear about no ETA's lol.
Click to expand...
Click to collapse
deadman96385 said:
I actualy have a Triboot,Ubuntu, Desktop,Hard Wired, i have deleted the folder am repulling down on to my extra hardrive. will edit when it finsh's.
Click to expand...
Click to collapse
Do you guys mind if i come on this project with you? This sounds very interesting...
I'll be downloading this at work tomorrow - 64 bit Xubuntu 11.10 (single boot), desktop, wired.
yeah this looks good, may have to give this one a crack in the near future
Open web os ported to galaxy nexus
http://www.theverge.com/2012/9/28/3425382/open-webos-galaxy-nexus-port
Sent from my Toasted Marshmallow using xda app-developers app
ggolemg said:
Open web os ported to galaxy nexus
http://www.theverge.com/2012/9/28/3425382/open-webos-galaxy-nexus-port
Sent from my Toasted Marshmallow using xda app-developers app
Click to expand...
Click to collapse
Just saw that on Cnet
Sent from my Dark JellyBellyG1 using xda app-developers app
Howdy dudes! Any news?
As good a place as any to post this.
Pio-masaki.com is being shut down due to a Cease and Desist order sent against the host by Google and homeland security. I have no idea why, however until this is sorted out, and to avoid any possible or further legal issues, the site is down for a period of time that can be a day or forever. This includes any and all ROMs, kernels, gapps packages, for any and all devices, that were hosted on pio-masaki.com.
I apologize in advance for this as I know some ROMs are only available at pio-masaki.com, but it is out of my hands, the host has to consider their own safety, and has my 100% agreement and backing in taking down the site until the matter is resolved.
As this is a very large matter, and one that has us incredibly scared, I'm retreating from android for the time being, until I know what it was that I did that was illegal, and may return once this is cleared up and blows over.
After this is cleared up the hosting for pio-masaki.com may still remain offline as the hoster has some personal issues with me at this point and may or may not continue to host for me, should we resolve our differences it may return.
If by some chance Google or whoever sent the C&D notices this, I urge you to contact me as I was responsible for what was hosted, and would genuinely like to know what the issues are so we can get them resolved immediately.
I will be making similar postings or editings to any other ROM threads that link to pio-masaki.com.
As a favor I built Carbon ROM for a friend, and as it mostly works, he suggested I put it up for all of you guys to use, which I'm doing now :good:
Please refer to this thread http://forum.xda-developers.com/showthread.php?t=2137013 for a better understanding of the ROM and what it can do and features, otherwise here is some options it has:
-PIE!
-HALO
-Dark Carbon! Huge props to Slim Roms for coming up with this unique and awesome feature.
-Lockscreen theming
-CM skinny battery is back!
-Volume key lock on silent mode option
-Backup tool - if you're flashing a new version of Carbon and already have the required version of gapps installed, it will be backed up and restored during install. This applies to system apps and custom host files as well. Please note that you should only dirty flash from Carbon to Carbon. It's ok if it's another version or a nightly - just not over other roms. Super handy for you crack flashers. Make sure you've got the most recent Gapps though, and if you're flashing from a factory reset, you'll still need to install it after install of course.
-Long pressing the "clear recents" button clears the cache
-AOKP's awesome new navbar settings
-NFC polling mode for when you want to keep your screen off and scan tags
-MMS and call "breathe" feature. Makes the notification icon fade in and out.
-Mute dings when changing volume
-Disable/enable CRT effect on screen on/off.
-3rd party keyboard bug fixed
-deodexed again
-stability and speed enhancements
Who is Carbon?
andros11
BigShotRob
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00
Change Log
7.18.13
Initial release build, corrected non operational WiFi
8.06.13
Updated source, dock should now be fully funtional
9.15.13
Updated to 4.3
Built with CM's device tree and kernel source
As my tester no longer has this device, this is completely untested, reports are welcome!
THANKS, CREDIT, PROPS
Team Carbon
CyanogenMOD
AOKP
Google
Linaro
diesburg - for testing and suggesting releasing so you guys enjoy it also
Drgravy - 4.2 builds based on his device/vendor tree and kernel binary, and whoever else is included in the making of those.
Notes, info, warnings
First and foremost, I do NOT own this device, I don't even own an Asus device, and not counting the N7, never have. I am building this blind and rely only on feedback from testers and users. As such, please remember this as you decide to yell about broken stuff.
This isn't a primary development device for me, I'm always willing to offer support on anything I release, but please don't expect daily builds. Weekly, perhaps, but it's mostly as I have the spare time to.
4.2 Bootloader only, I can not be held responsible if you flash this on any other bootloader and whatever happens, happening.
Information concerning updating and installing the correct bootloader and recovery can be found at the following:[GUIDE]Upgrade TF300t to Jellybean 4.1 or 4.2, root, recovery & remove bloatware by krabappel2548 - please remember this is for the 4.2 Bootloader ONLY, please follow instructions for updating to 4.2 bootloader and recovery!
[GUIDE] How to install Universal Naked Drivers by tobdaryl - for setting up your PC to get going so you can root/flash/recovery/ROM your device.
[VIDEO Overviews and How To's] ASUS Transformer Pad 300 (TF300T) by AllAboutAndroids - for those who need or prefer video style instructions, swing by here and watch what they have to offer.
I'd be happy to add any additional information as it's needed, as I don't own the device I'm not real familiar with it and whats available information and utility wise. These looked like very informative threads to help users who may need a little guidance to getting ready to use Carbon on their device.
BUGS
BT does not work Rebooting will have BT working.
Some keys on the keyboard do not work
Whatever else?
Where can I get this?
You can visit pio-masaki.com, it's under the TF300T header, builds are always dated, and if multiple builds of the same date are made, they will include sequential build numbers, such as B2, B3, etc.
For those who don't want to go find it, here you go:
http://www.pio-masaki.com/index.php?dir=TF300T/Carbon/
Hosting for the site is made possible by diesburg for the best user experience and speed.
FAQ
Q. BT doesn't work!?
A. Reboot, BT should fire up as normal after the first reboot.
Q. HALO isn't appearing after I enabled it in settings, what gives?
A. Go into any UI besides Tablet UI (phablet, whatever you want to call its default UI mode) then reboot, enable HALO in settings, then pull down the statusbar and tap the circle icon, HALO will then appear. You can then go back to Tablet UI if you wish.
Q. I want to throw money at you / throw my daughter at you / bear your children! How can I do this?
A. Money can be freely donated (freely donated meaning in no way required or expected, however loved and appreciated as it's my only income and diapers are expensive) by clicking the donate to me link under my name to the left. Also please consider donating to diesburg for the hosting he has paid for. For throwing daughters around, maybe seek therapy, she may not like it. For children bearing, my wife wouldn't care for it, so get that out of your head. I also accept devices (old/broken/new/wet/bricked/whatever).
Kernel source: https://github.com/CyanogenMod/android_kernel_asus_tf300t
Device tree used: https://github.com/CyanogenMod/android_device_asus_tf300t
Fancy seeing you here
Sent from my Transformer Pad TF300T using Tapatalk 4 Beta
As he posted above, when I tested, BT won't turn on. Some shortcut keys on the dock don't work. Both battery meters and the dock battery seem to be working. FYI, if you switch the UI mode to tablet mode or something, it requires a reboot for it to take. I think there may be a couple small issues with Halo. Enable halo and download any file from any site using the browser and you should see what I saw.(Hard to explain, but the download progress in the status bar never goes away, jacks your whole status bar)
And keep in mind what pio_masaki said, he doesn't have this device. So if you need help with something in the rom, how to or something, he may not be able to help, I will help as much as I can since i actually have the device. Please don't bomb him with ETA's . His main priorites for development of ROM's are for devices he owns and AFAIK, that will not change, he will release new builds when he does and until then, wait patiently.
Sent from my TF300T using Tapatalk
wigginst said:
Fancy seeing you here
Sent from my Transformer Pad TF300T using Tapatalk 4 Beta
Click to expand...
Click to collapse
HAHA hey I didn't know you had one of these, you traitor!:highfive:
Just got it. Wife has the thrive now (still running fine now).
Sent from my Transformer Pad TF300T using Tapatalk 4 Beta
wigginst said:
Just got it. Wife has the thrive now (still running fine now).
Sent from my Transformer Pad TF300T using Tapatalk 4 Beta
Click to expand...
Click to collapse
I need to sell the excite and get one of these :beer:
I have really liked it so far and has a good development community.
Sent from my Transformer Pad TF300T using Tapatalk 4 Beta
Just want to throw a reminder out... this is for 4.2 bootloader.... if you're on 4.1 you will have to upgrade.... if you have any doubt about what you are doing with the upgrade process and flashing the new recovery, please, for the sake of your own tablet, read, read, read, until you are sure about what you are doing. If you need help with upgrading the bootloader and flashing new recovery, let me know and we will post links to threads that have directions.
Sent from my TF300T using Tapatalk 2
cool to see this here going to dl and flash this
I'll let you know how it goes
pio_masaki said:
I need to sell the excite and get one of these :beer:
Click to expand...
Click to collapse
that would be a dream come true....lol....
Sent from my TF300T using Tapatalk 2
---------- Post added at 05:45 PM ---------- Previous post was at 05:18 PM ----------
Ok, just want to report that after one reboot, bluetooth turns on now. On initial install and first boot it wouldn't. I have nothing to test it with ATM though to see if it actually pairs with something.
Sent from my TF300T using Tapatalk 2
I am going to try this right away. Great to see a brand new ROM for our devices!
Man! I just flashed Jellybam v9.2 and nooww it gets released I tried building this before, but it didn't work! -_- what did you have to do to get this to build correctly. I added the device tree and vendor tree, updated the vendorsetup.sh and added a carbon.mk to the device tree, but it didn't build correctly.
Sent from my TF300T using xda app-developers app
andrewnelson23 said:
Man! I just flashed Jellybam v9.2 and nooww it gets released I tried building this before, but it didn't work! -_- what did you have to do to get this to build correctly. I added the device tree and vendor tree, updated the vendorsetup.sh and added a carbon.mk to the device tree, but it didn't build correctly.
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
Likely the carbon.mk wasn't correct then. I build it for a few devices so I'm used to the way carbon builds so it didn't take much ton get it going here, drgravy's trees were 99% set already.
I'll put the trees I used up, I don't usually put them up until it works. Sometime tonight for whoever wants to tinker with the remaining issues.
pio_masaki said:
Likely the carbon.mk wasn't correct then. I build it for a few devices so I'm used to the way carbon builds so it didn't take much ton get it going here, drgravy's trees were 99% set already.
I'll put the trees I used up, I don't usually put them up until it works. Sometime tonight for whoever wants to tinker with the remaining issues.
Click to expand...
Click to collapse
Gotcha! Makes sense. Yeah I'd like to see how you got it to work with the carbon.mk. I'd like to build it for my phone too. Thanks
Sent from my Inspire 4G using xda app-developers app
andrewnelson23 said:
Gotcha! Makes sense. Yeah I'd like to see how you got it to work with the carbon.mk. I'd like to build it for my phone too. Thanks
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
I run carbon on all my devices lol. Sadly I have to build it myself since none are supported by the team.
pio_masaki said:
Likely the carbon.mk wasn't correct then. I build it for a few devices so I'm used to the way carbon builds so it didn't take much ton get it going here, drgravy's trees were 99% set already.
I'll put the trees I used up, I don't usually put them up until it works. Sometime tonight for whoever wants to tinker with the remaining issues.
Click to expand...
Click to collapse
if you put up a frameworks_base I may submit a pull request to get the dock functions working
Drgravy said:
if you put up a frameworks_base I may submit a pull request to get the dock functions working
Click to expand...
Click to collapse
Its on their github, carbondev. I'm sure its broken because the asusdec and something else didn't get along with the framework yet, unlike cm there's no real dock support in Carbon. Now that WiFi and I suppose BT are working it looks like only the dock stuff is left.
Gr88 to see pio posting stuff for our tab
His builds are quality :thumbup:
Will d/l and report back.
DNA | ⓣⓐⓟⓐⓣⓐⓛⓚ | TF300T
This ROM is in no way suitable for daily use and is only shared so that other fellow developers can take a look and maybe provide fixes to one or multiple things on the "not working" list.
Take it as a very early proof of concept.
ROM DOWNLOAD: http://www.androidfilehost.com/?fid=23501681358554238
What I did to get this far...
1. I took the MI3W miui-germany ROM
2. I unpacked the MI3W's ROM
3. I unpacked the boot.img of the MI3W ROM (zImage, dt.img, ramdisk)
4. I patched the fstab.qcom and init*.rc files to match the Find 7a
5. I unpacked the latest OmniROM for Find7a
6. I unpacked the boot.img of OmniROM (zImage, dt.img, ramdisk)
7. I copied zImage and dt.img from OmniROM's extracted boot.img into MI3W's extracted boot.img
8. I repacked the MI3W boot.img
9. I bundled the MI3W system partition with the modified MI3W boot.img and uploaded it onto the internet for someone else to iron out the remaining bugs
What seems to work...
*) Basic Operation (MIUI apps, status bar, well what you would expect really)
*) Bluetooth
*) Wired Headset / Bluetooth Audio
*) RIL / Mobile Data
*) GPS
What doesn't work... yet...
*) WiFi (there seems to be some issues with wcnss / pronto / prima, this one is bad...)
*) Random Reboots / Blackscreen Glitches (from what kmsg tells me it seems to be related to wcnss, aka. WiFi drivers causing a critical error in kernel every once in a while, fix WiFi and this error will fix itself)
*) Speaker Audio
*) Rotation Sensor (and probably others)
*) Vibration
*) Skyline Notification Light
*) NFC
For pictures check the thread at the oppoforums: http://www.oppoforums.com/threads/rom-miui-port-for-find-7a.17409
Good things always have the obstacles.
You've done your part. And let other(s) help you.
I don't have knowledge about cooking a ROM.
But I think someone can help. @Entropy512, can you look at this one?
If you want mae some cool port, i thikn sense rom is good candidate...
Great work
hey there mrcoldbird,
great work so far...keep it up..will definately help support you on this when it is up and running..i am not a dev but if you need someone to just bug report i am there for you,will keep my eyes n ears peeled on the thread and as soon as it's near ready i will flash and help you anyway i can...thank you for all your hard work so far
Right now we need developers involved in this. We know the countless obvious bugs.
Just have to fix them.
Awesome work. Thanks bird. Any chance you want to try lewa os while you're at it. I personally think it is better. I imagine just how busy you are but just wanted to throw it out there
Porting really should only be done when there is no source available for said ROM.
For unicorn a source rebuild might be better.
MrColdbird said:
Porting really should only be done when there is no source available for said ROM.
For unicorn a source rebuild might be better.
Click to expand...
Click to collapse
I updated my post. You should really check out lewa. It has find 5 official support
uppon2 said:
I updated my post. You should really check out lewa. It has find 5 official support
Click to expand...
Click to collapse
no news about this rom
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
MrColdbird said:
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
Click to expand...
Click to collapse
ok thanks for answer. i love miui rom. i think it can be the best rom for find 7a
good luck
---------- Post added at 12:23 PM ---------- Previous post was at 12:21 PM ----------
MrColdbird said:
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
Click to expand...
Click to collapse
if you need help for test rom tell me. i have a lot of time for this.
when i try to install your rom twrp failed. do you know why ?
jazzypit said:
no news about this rom
Click to expand...
Click to collapse
Lewa OS website
YouTube video
uppon2 said:
Lewa OS website
YouTube video
Click to expand...
Click to collapse
no rom for oppo find 7a
do you have a link for test ?
jazzypit said:
no rom for oppo find 7a
do you have a link for test ?
Click to expand...
Click to collapse
No. That is what I'm asking for; a build for lewa for the find 7.
uppon2 said:
No. That is what I'm asking for; a build for lewa for the find 7.
Click to expand...
Click to collapse
Which doesn't belong in this thread. Take it elsewhere.
justin654 said:
Which doesn't belong in this thread. Take it elsewhere.
Click to expand...
Click to collapse
Lewa OS is extremely similar to MIUI and that is why I even bothered to mention it. I know the developer is having some trouble with MIUI so I thought it would be useful and helpful to mention Lewa as it might be a project that will help the development of either or rom.
Please don't take a blunt tone with me (if that's what it was) as it only makes you look arrogant. Taking in to account our post and thanks scores it is quite clear who has contributed in a more positive way towards XDA. On that note; you might also want to thank MrColdbird in the OP for his contribution, which you have not done as of yet but you seem to be poking your nose in to the thread
That is all
Edit* I apologise MrColdbird if my suggestion was unwarranted.
MrColdbird said:
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
Click to expand...
Click to collapse
I am setting up a build environment and will be looking in to it; starting with wifi. I think I might check out lewa as well.
good luck
I've pm one of the Miui dev from note 1 community, and hope that he willing to lend his hand for you @MrColdbird.
Mr @Gerrett, can you help him? If you got some free time. I know you so busy. But at least, just a little guide for him.
FareedYusoff said:
I've pm one of the Miui dev from note 1 community, and hope that he willing to lend his hand for you @MrColdbird.
Mr @Gerrett, can you help him? If you got some free time. I know you so busy. But at least, just a little guide for him.
Click to expand...
Click to collapse
Actually I've got 99% of the issues resolved already by using a different port-rom in conjunction with a few OmniROM injects.
At the moment only the proximity sensor (screen off on holding the phone to your ear) and nfc are broken, lte works, but needs to be reselected every time the phone reboots via the service menu (dialer code).
Sadly, I'm not allowed to share that (quite nicely working) ROM just yet as I switched port-bases to a unreleased chinese one in favor of the MI3W port-base.
Until that chinese author releases his first public port base-rom I'm kinda bound by the promise I gave not to unveil things early.
Just hang in there, it shouldn't be long until you guys have MIUI on Find7a... all I can tell you is that it works nicely and without any critical flaws I can see except those mentioned above (which we will get fixed too eventually).
MrColdbird said:
Actually I've got 99% of the issues resolved already by using a different port-rom in conjunction with a few OmniROM injects.
At the moment only the proximity sensor (screen off on holding the phone to your ear) and nfc are broken, lte works, but needs to be reselected every time the phone reboots via the service menu (dialer code).
Sadly, I'm not allowed to share that (quite nicely working) ROM just yet as I switched port-bases to a unreleased chinese one in favor of the MI3W port-base.
Until that chinese author releases his first public port base-rom I'm kinda bound by the promise I gave not to unveil things early.
Just hang in there, it shouldn't be long until you guys have MIUI on Find7a... all I can tell you is that it works nicely and without any critical flaws I can see except those mentioned above (which we will get fixed too eventually).
Click to expand...
Click to collapse
Quite fast actually. By the way, I just can wait and see your nice work.
I'm trying to help, but that's all I can do right now. All the best on your effort.
I appriciate your hardwork. :highfive: