Develop Bugs

Sneak peak - CM7 for Flipside

Note: laidaxin has since released his CM7 rom over Here. It's further along and stuff, so this will probably won't change anymore
Sneak peak of CyanogenMod 7 ported to the Motorola Flipside!
Using this recovery: http://forum.xda-developers.com/showthread.php?p=22073717
Running pretty smooth..
What needs to be fixed before an alpha release:
- Phone network
- Sound
- Backlight won't turn off
A few other things don't work yet (such as camera, GPS)
PS: I'll probably re-use this thread for release

WinSuk said:
Sneak peak of CyanogenMod 7 ported to the Motorola Flipside!
Using this recovery: http://forum.xda-developers.com/showthread.php?p=22073717
Running pretty smooth..
What needs to be fixed before an alpha release:
- Phone network
- Sound
- Backlight won't turn off
A few other things don't work yet (such as camera, GPS)
PS: I'll probably re-use this thread for release
Click to expand...
Click to collapse
Wish I was able to test for you and help out. Good job tho. Good luck.

Appreciated
what else u want to tell ur friends here is when is the alpha one coming...!
any update on issues currently being faced...?

Is this for real?
I thought CM7 required a different kernel?
I am excited to see how much free internal storage the OP seems to have...
Sent from my MB508 using Tapatalk

WinSuk said:
Sneak peak of CyanogenMod 7 ported to the Motorola Flipside!
Using this recovery: http://forum.xda-developers.com/showthread.php?p=22073717
Running pretty smooth..
What needs to be fixed before an alpha release:
- Phone network
- Sound
- Backlight won't turn off
A few other things don't work yet (such as camera, GPS)
PS: I'll probably re-use this thread for release
Click to expand...
Click to collapse
Great! here wait so long for a Dev that could help with the FlipSide... after months of use it I am amaze about the specs (have a 720mhz cpu that could be OverClk to 1Ghz, and with a rom with system clean may I suspect that it may could have around 256Mb of ram taht with apps2sd make it a very descent droid with keyboard! )and the confidence of the harware components of the FlipSide, is amazing how well works the 3g Networks on this... really deserves a better Rom and a CyanogenMod version will be AWESOME and for sure will make the Flip shine!
Thanks for take time to dev for our humble Flips, and waiting eagerly for your release... The screenshots seems very nice and promising.
Thanks again and best regards!

Overclocking needs a custom kernel (AFAIK), and that can't be done on this device (for now).
The Defy has some sort of overclocking though, so it's possible...
The Flipside I'm using isn't mine (yet) so I can't work on it every day. Also depends on if I want to or not
I'll try to work on it tomorrow

CyanogenPure?

I love CyanogenMod, I really do. It is constantly improving and the devs working on it obviously work very hard to keep things running smoothly. However, with a codebase this large, constant improvements inevitably leads to a fairly consistent stream of new bugs amidst the improvements. I understand that nightlies are not intended to be used as daily drivers, although usually they are stable enough for most here at XDA.
Acknowledging all of this: I can't help but wish on some days that I could take the excellent skills/care/devotion of the CyanogenMod team and have them devote a fraction of their work to create a pure, optimized AOSP ROM. No mods, no community apps, and (hopefully) no bugs. This would be an incredible stop-gap between the initial build of a new CM nightlie (say, CM11) and the inevitable stable release.
This is NOT a statement against the added mods/apps to CyanogenMod (File Manager, Apollo, DSP Manager, etc.), I am very much of the opinion that these additions are beneficial, even necessary to the growth of CyanogenMod.
I do not expect this to happen, and I especially do not expect them to go back through CM10 and line-by-line strip all of their adjustments/additions. I understand that they are all very busy at work to keep us happy, and I appreciate that. Think of this as wishful thinking from a big fan.
Am I alone in this opinion?

it is called an AOSP rom. in this case vanilla. get a nexus device for that

Obviously, but I think you're missing my point...or you didn't read my post.

ohfoxxxycole said:
create a pure, optimized AOSP ROM. No mods, no community apps, and (hopefully) no bugs.
Click to expand...
Click to collapse
A vanilla android rom with a custom kernel
Sent from my SPH-L710 using xda app-developers app

XxSilent.NightmarexX said:
A vanilla android rom with a custom kernel
Click to expand...
Click to collapse
Yes, but done by devs that know what they're doing.

Every single dev here knows what they are doing. Plus aosp is easy to compile for any device
Sent from my SPH-L710 using xda app-developers app

I don't see any after a quick search. I've used pure vanilla ROMs on my evo/evo3d and they were pretty terrible. I just assumed, by prior experience and lack of vanilla roms here, that they were tricky.

no, thats just because AOSP roms lack features that people crave from CM or AOKP

Alright, so we're back to my initial post now.

In other words an aosp pure android rom is not people look forward to. Cm10 stable rom is there and probably with like one minor bug or two.
Sent from my SPH-L710 using xda app-developers app

I know how you feel; I wish they would release a stable ROM for those that prefer stability over speed/features

EXACTLY. i love how hard the devs work to improve android and add features but until its possible to get a stable rom with these features I'd prefer simple, pure vanilla with all work going towards stability. Maybe I'll start on that one day
Sent from my SPH-L710 using xda app-developers app

ohfoxxxycole said:
EXACTLY. i love how hard the devs work to improve android and add features but until its possible to get a stable rom with these features I'd prefer simple, pure vanilla with all work going towards stability. Maybe I'll start on that one day
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
You can't ask for optimization with stability. The nightlies are there because that's what they're trying to achieve, if it's not stable enough for you - don't use it. Go back to TW. That's the closest to pure stable for this device you're going to get. There are -always- bugs, even in the most fine tuned software, because it's all about what the user puts on their devices and how it interacts with the system.
Plus, not too long ago CM released the CM10 Milestone 2. It's stable enough for daily use. Give that a shot. If it's not to your liking, pull CM's device tree into a freshly synced repo of AOSP and compile it. See how easy it is to get it working.

There are -always- bugs, even in the most fine tuned software, because it's all about what the user puts on their devices and how it interacts with the system.
Click to expand...
Click to collapse
this is true, but i'd be using this with mostly stock software + social network feeds and games only
the milestones are a great idea, and probably the closest thing im going to get to this, but they are still snapshots of mostly stable aosp with many many tweaks to keep modifications that i may or may not use stable. not exactly ideal, but thanks for the suggestion. i'll probably stick with the newest m build when it is ready.
im not asking for cms device tree compiled as it is, or anything at all. im just hoping that before or adjacent to cm11 getting going with mods and tweaks that they will release builds tailored to vanilla and nothing else, concentrating only on bugs before adding things and testing them and adding things and breaking things and testing them and so on and so forth. i feel im not communicating this efficiently and im sorry

$MyName said:
You can't ask for optimization with stability. The nightlies are there because that's what they're trying to achieve, if it's not stable enough for you - don't use it. Go back to TW. That's the closest to pure stable for this device you're going to get. There are -always- bugs, even in the most fine tuned software, because it's all about what the user puts on their devices and how it interacts with the system.
Plus, not too long ago CM released the CM10 Milestone 2. It's stable enough for daily use. Give that a shot. If it's not to your liking, pull CM's device tree into a freshly synced repo of AOSP and compile it. See how easy it is to get it working.
Click to expand...
Click to collapse
Does the bottom mic work on M2? What about the data drops that constantly happen? Does it transition well from LTE to 3G, vice versa?
And these are serious questions, I'm not trying to be a [email protected] at all.
I have a 20 month old baby girl so I do a lot of video recording, so the bottom mic is important to me since the top one doesn't pick anything up unless you're basically speaking directly into it. I do a lot of business through my phone, so a reliable data connection is obviously very important too. I've had BB6 on my phone for about a week now, and I absolutely love it...with these two exceptions. It seems they're both problems with all AOSP ROMs. If they get fixed sooner rather than later, there will be zero reason to have TW ROM for me.
EDIT: And GPS seems to take quite a bit longer to lock on compared to TW.

hayzooos said:
Does the bottom mic work on M2? What about the data drops that constantly happen? Does it transition well from LTE to 3G, vice versa?
And these are serious questions, I'm not trying to be a [email protected] at all.
I have a 20 month old baby girl so I do a lot of video recording, so the bottom mic is important to me since the top one doesn't pick anything up unless you're basically speaking directly into it. I do a lot of business through my phone, so a reliable data connection is obviously very important too. I've had BB6 on my phone for about a week now, and I absolutely love it...with these two exceptions. It seems they're both problems with all AOSP ROMs. If they get fixed sooner rather than later, there will be zero reason to have TW ROM for me.
EDIT: And GPS seems to take quite a bit longer to lock on compared to TW.
Click to expand...
Click to collapse
I was using m2 for quite a while before I switched over to bb6. In my time playing with m2 I found that video recording was fine and data connectivity took about 10 seconds longer on a reboot. Other than that I've experienced no data drops.
To add to this, YMMV. I'm not sure if my phone is different somehow but I've never had any of these problems that people describe with data drops at random.
Edit:
Also, as far as lte/3g hand off goes, I'm unable to test as I'm not in an lte area. As for GPS, it takes about 7 seconds to lock on in a room with no windows. Tested on slimbean, so again YMMV
Sent from my SPH-L710 using Tapatalk 2

Just try looking into building aosp from source its really not that hard it will just take some time. You could even use the device tree for d2spr from cm so you really will just be using pure stock
Sent from my SPH-L710 using xda app-developers app

ohfoxxxycole said:
I don't see any after a quick search. I've used pure vanilla ROMs on my evo/evo3d and they were pretty terrible. I just assumed, by prior experience and lack of vanilla roms here, that they were tricky.
Click to expand...
Click to collapse
You're clearly smoking some good crack. AOSP ROMs for the E3D are awesome right now.

Months ago
Sent from my SPH-L710 using xda app-developers app

[ROM][14-02-13][Flinny] Andromadus - AOSP4.2.2[9]

Andromadus - Test Builds
To start with here you will find test versions of ROMs built by me from the Andromadus github repo http://github.com/Andromadus, think of them along the same concept as nightly builds just not every night These are development ROM's, if you want to run bleeding edge development ROM's and at least know how to use adb and logcat then you might find something of interest here. If you require something that works 100% of the time all of the time then this might not be for you. That said you can always give it a try and if it doesn't work restore your previous nandroid backup!
What IS Andromadus?
Initially it was a group of people who got together to make ICS work on the HTC Desire Z because nobody else seemed to want to support devices with physical hardware keyboards/trackpads. Whilst the idea stays the same It has grown slightly to support some other hardware and some of the work we have done is now used in many other devices. Andromadus builds of CM10 or CM10.1 are basically CM sources with a few additional tweaks or additions to support our phones.
1. New versions will be added as and when I feel there are enough changes to warrant one, don’t ask when the next version is coming.
2. If we decide to release a "Stable" version of these roms they will be published in another Andromadus thread.
Direct all your queries with release versions to that thread and in the same vain do not discuss these releases anywhere but here.
3. I will do as best I can to answer questions but if you don't get an answer from me I'm sure somebody else will be along to help. Help each other and I have more time to spend fixing things!
4. Don't ask for what's changed since the previous version, have a look at the recent submits on the Andromadus github if you want to know or wait for the mini changelogs when I post a new release.
5. If there is something in particular to test it'll be mentioned!
6. As always if you didn't wipe between installations then at least verify that the problem exists on a clean install before posting here. Nandroid/superwipe/install/check at the end of the day you can always restore your nandroid if the problem is reproducible on a clean installation. If you can't be bothered to try this then I really can't be bothered to try to help you :>
7. All that said ensure you make a nandroid/backup before hand. I take no responsibility for what you do to your phone with these ROM.
8. Whilst I can't stop you I would rather these builds were not used as a base for any ROM/MOD/ETC. The source is all available if you want to do your own builds with which you can do whatever you like.
9. Tell us what works/what's worse/what's better but don't ***** when something breaks or isn't fixed yet, report it and move on.
10. Sometimes people forget that we do this for fun, for ourselves, and sometimes your super important issue is way down on our personal list of things to be fixed.
If you ignore any of the above you will in turn be ignored.
Now that's all out of the way as always have fun
As usual you need to flash the ROM then GAPPS.
Checkout http://andromadus.flinny.org for links/files/changelog's
This a team/community effort, I'll not list everyone who has helped along the way here that list is in the beta thread but I will say thanks to all of them again and obviously anyone that has been missed.

Reserved

Hi Flinny, great job on the AOSP builds they are running perfect. I only had one satback sins build 4. Suddenly my gallery stopt working and dropbox to. Because of the gallery problem my camera won't boot either. I flashed build 5 but I had the same problem. Build 4 was flashed with a full wipe and build 5 was flashed as update that the reason of course why the problem didn't left but sometimes it helps Does this sound familiar? Greetz Munky

I tested it last evening but have many FC message about "aosp keyboard" even with the physical keyboard
I wiped all but still the same message going back to cm10.1

Ok I'm a little rusty on the details at the moment but: AOSP means that you want it to get as close as stock experience as you can get right? (I'm really looking for a G-lite thing but then with ICS/Jelly Bean, sort of Nexus feel but then for our Desire Z)

What's everyone's opinion on these AOSP builds? To me they seem more stable and faster than CM. I kinda miss CM a little though, but not the lag.
Sent from my HTC Vision using xda app-developers app

I know that this is a dumb question and the answer is probably within the other thread, but... Ah heck, now it's just that I'm too lazy to look for the solution LOL...
But I installed AOSP 4.2 v6 last night and so far I'm not experiencing any major problems (except for FCing when I edit a picture and a bit of confusion adjusting to some new features LOL)... But when is this project going to be merged with CM? There are LOTS of creature comforts (e.g. silence during night hours, T9-style contact search, etc.) that I'm used to with the CM-optimized version that I kinda miss and only noticed that it was gone when I flashed it (I was under the impression that those features were all standard?)
Sorry to pester and thanks in advance.

EdWaRdW818:
Here you've got CM10.1 which is based on AOSP 4.2
http://forum.xda-developers.com/showthread.php?t=2031678
Flinny:
Could you add init.d support to the rom or fix it? I see that there is a placeholder for scripts and there is one script, but it's not executed on boot (with 755 permissions).

Eddy130306 said:
What's everyone's opinion on these AOSP builds? To me they seem more stable and faster than CM. I kinda miss CM a little though, but not the lag.
Click to expand...
Click to collapse
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)

google ears
EDIT: Sorry wrong thread
BTW: how can I delete my post?

I can't find changelog in your site flinny can you link it ?!
Inviato dal mio HTC Vision con Tapatalk 2

zofox said:
I can't find changelog in your site flinny can you link it ?!
Inviato dal mio HTC Vision con Tapatalk 2
Click to expand...
Click to collapse
http://andromadus.flinny.org/?q=node/2

This is absolutely the smoothest 4.0+ ROM I have ever used. Might switch to CM10.1 though for more features.

adamz667 said:
EdWaRdW818:
Here you've got CM10.1 which is based on AOSP 4.2
http://forum.xda-developers.com/showthread.php?t=2031678
Flinny:
Could you add init.d support to the rom or fix it? I see that there is a placeholder for scripts and there is one script, but it's not executed on boot (with 755 permissions).
Click to expand...
Click to collapse
catachresistant said:
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)
Click to expand...
Click to collapse
Oh jeez... Either I had a total brain fart and completely missed the link or it got posted anywhere from the time I posted it to the catching up of 14+ hours of sleep (I only slept 7 hours across 3 days LOL), but I guess CM10.1 is already posted. I'll download it and see what's up. Thanks for not flaming me guys. I would've gotten the N4 but I'm not a big fan of LG (had countless bad hardware experiences) and my phone is somewhat last on my "to upgrade list", so thanks for everybody's help and keep up the good work! There's some top quality Münchner Bier mit your name on it once I get some disposable income

catachresistant said:
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)
Click to expand...
Click to collapse
No I have not.
Sent from my HTC Vision using xda app-developers app
---------- Post added at 02:11 PM ---------- Previous post was at 02:00 PM ----------
LAMER_CZ
That is strange. Which recovery are you using? Don't use clockworkmod as they're always full of glitches and bugs. Don't use ROM Manager to flash ROMs either as they as well have glitches. I recommend doing everything in recovery. If you do have clockworkmod I recommend flashing 4ext as it has more features and can make your phone a little faster
Sent from my HTC Vision using xda app-developers app

Ok I just went ahead and installed it. This is exactly what I need for a ROM on my Desire Z! Thanks Flinny, and keep up the good work!
Now my experience with this ROM:
- I just fly trough my home screens and menu's, it runs fluently!
- When at stock speeds (so 1Ghz) I sometime run into problems booting up the settings. I just hangs there for 4+ seconds untill it actually shows the settings. Setting clockspeeds to 1,8Ghz fixes this most of the times, but it's something you might want to look into (Or don't, it's your ROM)
- The above also happens with some apps.
I don't run swap or any other optimization, so I don't know if it's my problem or a ROM problem, but if you want me to do some more testing just tell me what I need to do

Boot Loop
Thanks for the work, this is a great ROM, just thought I would pitch my issue I had.
Im currently testing an app and set the device to use 2g only as I wanted so see how quickly it pulled in my data on a slower connection. If you leave it in 2g mode and reboot it appears to get stuck in a boot loop.
Hope this is helpful.
Cheers

usc911 said:
Thanks for the work, this is a great ROM, just thought I would pitch my issue I had.
Im currently testing an app and set the device to use 2g only as I wanted so see how quickly it pulled in my data on a slower connection. If you leave it in 2g mode and reboot it appears to get stuck in a boot loop.
Hope this is helpful.
Cheers
Click to expand...
Click to collapse
I doubt that has anything to do with the "2g" setting since the radio doesn't come on until after it is booted up. Maybe that application you're testing screwed something up?

Authorita said:
I doubt that has anything to do with the "2g" setting since the radio doesn't come on until after it is booted up. Maybe that application you're testing screwed something up?
Click to expand...
Click to collapse
The app is fine, I have been building it for a few weeks and runds fine on a nexus one, and a sapphire. I have tried flashing the 4.2.1 AOSP build and the CM10 build and exactly the same is happening.
Guess I'm just missing something :s

usc911 said:
The app is fine, I have been building it for a few weeks and runds fine on a nexus one, and a sapphire. I have tried flashing the 4.2.1 AOSP build and the CM10 build and exactly the same is happening.
Guess I'm just missing something :s
Click to expand...
Click to collapse
Do you think you could get a log of the reboot? Might help in figuring out why it is rebooting like that.

[Q] preliminaries prior flashing an A101

Hey there!
i'm pretty new to modding android and recently got an A101 from a colleague - i think still one of the two best devices in the 7" format with only the Huawei Medipad providing the same functionality.
Anyway, i'd love to try something new and am already rooted with ZeroNull's method wich worked like a charm. Now that i've read many threads in this forum the past week i'm a little bit concerned about some things. First of all, when i'm in stock recovery my power button isn't working, so i cannot make any input besides selecting the menu-entries. Is it likely the case, that i would be facing this issue when installing a custom recovery? Since TWRP has a touch gui i shoudn't be aware of this, right?
Further A101 specific questions i wanne be 100% sure of, since there's no A101-Forum:
- i'm fine with installing bootloaders like TWRP or CWM made for the A100?
- aswell ZeroNull's unlock bootloader method?
- which custom ROM's do support 3G? I'm thinking about pio_masaki's Jellytime Sosei, his CM10 build, or KEBBERSROM...(?)
rather an ubuntu related question:
Am i fine with installing the packages: android-tools-adb & android-tools-fastboot or do i need the full - Android-SDK?
The most important thing for me is to get rid of acers bloadware, so i'm planning to install TWRP followed by a nandroid backup and kiling them softly *fingerscrossed*
running StockRom: Acer_AV0141_A101_1.015.00EMEA_DE

VolkerPfosten said:
Hey there!
i'm pretty new to modding android and recently got an A101 from a colleague - i think still one of the two best devices in the 7" format with only the Huawei Medipad providing the same functionality.
Anyway, i'd love to try something new and am already rooted with ZeroNull's method wich worked like a charm. Now that i've read many threads in this forum the past week i'm a little bit concerned about some things. First of all, when i'm in stock recovery my power button isn't working, so i cannot make any input besides selecting the menu-entries. Is it likely the case, that i would be facing this issue when installing a custom recovery? Since TWRP has a touch gui i shoudn't be aware of this, right?
Further A101 specific questions i wanne be 100% sure of, since there's no A101-Forum:
- i'm fine with installing bootloaders like TWRP or CWM made for the A100?
- aswell ZeroNull's unlock bootloader method?
- which custom ROM's do support 3G? I'm thinking about pio_masaki's Jellytime Sosei, his CM10 build, or KEBBERSROM...(?)
rather an ubuntu related question:
Am i fine with installing the packages: android-tools-adb & android-tools-fastboot or do i need the full - Android-SDK?
The most important thing for me is to get rid of acers bloadware, so i'm planning to install TWRP followed by a nandroid backup and kiling them softly *fingerscrossed*
running StockRom: Acer_AV0141_A101_1.015.00EMEA_DE
Click to expand...
Click to collapse
Cwm and twrp are recoveries, not boot loaders, and are fine for the 101, no worries there. Everything for the a100 works for the 101 except the Roms, a100 ROMs on a101 kills 3g. You lose 3g, period. Cm10.1 I had some experimental 3g stuff in there but I never heard back on that.
Maybe I'll see about adding it to cm10.
Sent from my HTC DNA

pio_masaki said:
Cwm and twrp are recoveries, not boot loaders, and are fine for the 101, no worries there. Everything for the a100 works for the 101 except the Roms, a100 ROMs on a101 kills 3g. You lose 3g, period. Cm10.1 I had some experimental 3g stuff in there but I never heard back on that.
Maybe I'll see about adding it to cm10.
Sent from my HTC DNA
Click to expand...
Click to collapse
Thats too bad to hear but i was expecting this. Just thaught that CM10 could have 3G functionality since some friends are using cyanogen on their phones. And since Sosei lacks of GPS it's not an alternative for me either. After all i convinced my wife to buy the a101, so that we can use it as navigation aswell ;P
well well, i really would appreciate the 3G Feature in your CM10, but i dont wanne hassle so - just if you have time for it of cause.
greetings and thanks so far

VolkerPfosten said:
Thats too bad to hear but i was expecting this. Just thaught that CM10 could have 3G functionality since some friends are using cyanogen on their phones. And since Sosei lacks of GPS it's not an alternative for me either. After all i convinced my wife to buy the a101, so that we can use it as navigation aswell ;P
well well, i really would appreciate the 3G Feature in your CM10, but i dont wanne hassle so - just if you have time for it of cause.
greetings and thanks so far
Click to expand...
Click to collapse
It can have 3g just fine, I've asked a few times for the 3g ril files from 101 users wanting me to build for them, they always vanish and I never hear back about it.
A100 just had its rotation for builds last night / this morning so it'll come up again sometime between wed-fri I think. Been looking at updating the black bean build and maybe adding AOKP as well, I'll use them for testbeds. I may go ahead and just do an extra day on the A100 and see about getting a potential 3g build up for you.
Side note, sosei will use gps if you use the newer cm10 boot.img.
Current rotation is:
Nexus 7 holds priority as I've been invited to Team Sorcery as their N7 dev.
Toshiba Thrive 4.2 development, 4.1.2 updates and kernel work (voodoo sound) comes second as they've been extremely generous to me.
Droid DNA aosp porting as the device was pretty much donated
Slight GNex work as needed, rare
A100 is bottom/last as I don't own one, luckily fixes from the thrive usually directly move over to the A100
Other devices I don't own.
I have a few things planned for the A100 for some nice updates and releases to jeep you guys in a variety of ROMs, like AOKP and some updates to the cm9 kernel I use.
Sent from my Nexus 7 - JBSourcery 4.5

pio_masaki said:
It can have 3g just fine, I've asked a few times for the 3g ril files from 101 users wanting me to build for them, they always vanish and I never hear back about it.
A100 just had its rotation for builds last night / this morning so it'll come up again sometime between wed-fri I think. Been looking at updating the black bean build and maybe adding AOKP as well, I'll use them for testbeds. I may go ahead and just do an extra day on the A100 and see about getting a potential 3g build up for you.
Side note, sosei will use gps if you use the newer cm10 boot.img.
Current rotation is:
Nexus 7 holds priority as I've been invited to Team Sorcery as their N7 dev.
Toshiba Thrive 4.2 development, 4.1.2 updates and kernel work (voodoo sound) comes second as they've been extremely generous to me.
Droid DNA aosp porting as the device was pretty much donated
Slight GNex work as needed, rare
A100 is bottom/last as I don't own one, luckily fixes from the thrive usually directly move over to the A100
Other devices I don't own.
I have a few things planned for the A100 for some nice updates and releases to jeep you guys in a variety of ROMs, like AOKP and some updates to the cm9 kernel I use.
Sent from my Nexus 7 - JBSourcery 4.5
Click to expand...
Click to collapse
thats of cause comprehensible, since these iconias are quite old, right. And if i didnt needed the (3g)/hdmi (looking forward for ubuntu for android) i guess i would have baught an Nexus 7 aswell. However, in two weeks i got an exam and i'm investing way too much time right now in reading about all that stuff here so if you could direct me were to read about this 3g ril files or tell me how i can find them on the mashine i'll send it to you. I've read something about the build.prob but no mentions about 3g, cellular or ril or whatsoever in it. Also a "find" gave me nothing.
Unfortunately i have to read some annoying §&"/%§ now but i've set up the email notification now.
greetings

[WIP][ROM][DEV]Ubuntu Touch 5/7

Okay everybody, I want to start a WIP on this as it seems that we can get somewhere. The last dev seems to have dropped the project so I picked it up. :good:
***NOTE*** This is meant for development/testing purposes ONLY. It is in NO WAY for the faint of heart and you must follow ALL instructions or it will not boot! You have been warned!
As of 5/7/2013, the following things are working:
Camera (flash works, it takes pictures)
Sound (the only reason I know this works is because the shutter noise goes off in the camera app, there is no other way to test this right now)
The test apps (browser, notepad, gallery, camera, browser, phone, calculator, calendar, clock)
Power button (phone goes to sleep and wakes, hold the power button down to shut off the phone - the shutdown takes a second because it shuts down just like a linux kernel would - plug it in the charger to test this, it will vibrate once it is off)
Not working - just about everything else. Most items are still placeholders and there is a stability issue where the apps all close themselves after a few seconds which I am trying to figure out. There is no data or cellular connectivity of any kind. This may be fixable, however, since I was able to get the camera working by pulling the prebuilts from a different CM version. I'll keep experimenting with this. If you put the device to sleep, it does not wake up to the same brightness (it is dimmed) and you can not adjust the brightness right now (working on this as well, its a permissions issue in the kernel source but I haven't been able to narrow it down yet).
It is VERY finicky about how it is installed. I won't give any support for anything but TWRP 2.5.0.0
To install:
-Download the kernel zip and the latest daily from Ubuntu (I will post links later)
-Backup your current ROM in its entirety using TWRP - check every item on the list or you may have to go to a fresh install of your version you were running previously.
-In TWRP (once again, make sure its 2.5.0.0 because these are 2.5.0.0 specific instructions), factory reset but do an advanced reset, check dalvik, data, system, and cache. ***MAKE SURE THAT YOU DON'T FORMAT YOUR MICROSD***
-Install the kernel zip and do not wipe cache or dalvik
-Install the Ubuntu preinstalled image, once again make sure you do not wipe the cache or the dalvik.
-Do not do anything else, no fixing permissions or anything, just reboot
-Wait about 2 minutes for the lock screen to come up and then you can use it
I will keep working on the kernel - the other functions will not work until Ubuntu implements them.
This is my first time working with actual development - if anyone wants to give me a tutorial to get my project up on GitHub so everyone can work on it, I would be more than happy to do so.
Here are the links:
Kernel built 5/7/2013: http://d-h.st/185
Latest Ubuntu Touch base: http://cdimage.ubuntu.com/ubuntu-to...current/raring-preinstalled-phablet-armhf.zip
Since the source has been moved to Raring Ringtail, there should not be a need to update that link. Please note that the 5/7/2013 build is the one that I tested and be sure to let me know if it gets broken in the future.
Enjoy everyone and once again, if you want to contribute, I'm more than happy to set up a GitHub, I just need some basic help getting it started.

Thanks this looks very hopeful.
Sent from my SAMSUNG-SGH-I747 using xda premium

TheLastSidekick said:
Thanks this looks very hopeful.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I am hoping that development will take off. Ubuntu is set to start releasing alpha apps on the 16th so figuring out how to get a working kernel for it was top priority for me and nobody else seemed interested in doing it.
I've literally spent hours, lots of expletives, and other unpleasant things trying to get this built. I think I should have started working with CM BEFORE taking on UT but it paid off

Thank you sir,

Dling now
Sent from my Galaxy Nexus using xda premium

Flashed and everything went smoothly. Very pre-alpha, but alot of.stuff is working comsiderinf whaf it is. I wluld like to test this for any developer that wants to build it
Sent from my SGH-T999 using xda premium

ktetreault14 said:
Flashed and everything went smoothly. Very pre-alpha, but alot of.stuff is working comsiderinf whaf it is. I wluld like to test this for any developer that wants to build it
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I'm glad that you enjoyed what currently works.
I have done some work on the kernel but I need some help figuring out the WiFi. The drivers are proprietary Broadcom drivers so I need to see if anyone has gotten it to work on their Touch builds.
The rest of it is mainly just waiting on Ubuntu to stabilize - this isn't even considered an alpha at this point. Alpha starts May 16th.
Either way, I've managed to compile a kernel using cm-10.1-M3 (4.2.2) sources in preparation for UT's inevitable source upgrade from M1 (4.2.1) to M3. I'd post it but it doesn't have any different features from the M1 kernel up above.
I'll be updating it as Ubuntu releases new features or if I can get other things working on the build.

EtherealRemnant said:
I'm glad that you enjoyed what currently works.
I have done some work on the kernel but I need some help figuring out the WiFi. The drivers are proprietary Broadcom drivers so I need to see if anyone has gotten it to work on their Touch builds.
The rest of it is mainly just waiting on Ubuntu to stabilize - this isn't even considered an alpha at this point. Alpha starts May 16th.
Either way, I've managed to compile a kernel using cm-10.1-M3 (4.2.2) sources in preparation for UT's inevitable source upgrade from M1 (4.2.1) to M3. I'd post it but it doesn't have any different features from the M1 kernel up above.
I'll be updating it as Ubuntu releases new features or if I can get other things working on the build.
Click to expand...
Click to collapse
So, Ubuntu is using android stuff for these builds?
Sent from my SGH-T999 using xda premium

eggydrums said:
So, Ubuntu is using android stuff for these builds?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
The kernel is a CM base. Its a massive fork of CM that's kind of a royal pain in the ass to work with since its not been synced since they forked it and they've made major modifications to the code (all traces of Dalvik are gone, for example). You also have to make modifications to the kernel build so it functions more like a linux system, there are process patches that have to be applied to the kernel, etc.

Thanks for keeping this going. Not much is going on until Ubuntu pushes things out later this month. Everything will pretty much FC until we have the proper scripts.

Cannot wair for Ubuntu to be fully released, I would like to use this as a daily driver
Sent from my SGH-T999 using xda premium

charlieb620 said:
Thanks for keeping this going. Not much is going on until Ubuntu pushes things out later this month. Everything will pretty much FC until we have the proper scripts.
Click to expand...
Click to collapse
So you had the same issue with your build?
Admittedly, I never tried it because I was determined to build my own and yours was March dated. I had posted in the thread trying to get some assistance from you actually - but yeah, its certainly not usable right now.
Was your kernel a forced M1 or did you somehow find a way to get the nightly source to build? I've built M1 and M2 so far. Since I had the same results with both and UT is based off of M1, I haven't messed with M3.
I wish I could figure out the WiFi and the force close of apps - did you patch the kernel successfully? I added the proc patch as best I could (raw data paste but it didn't throw warnings so it must have worked - I'm not a programmer) and it didn't fix anything, apps still just close after a few seconds.
I was surprised that I got the camera and sound though just by switching CM versions. Maybe the same thing can happen with the WiFi? I noticed that it is being built as a module but I don't know enough about the Android kernel to reconfigure it as a built-in (I don't know if the Ubuntu kernel has the code for detecting all the hardware just yet, I'm guessing it doesn't). I've done lots of Linux kernel tweaking (I have toyed with it since Red Hat 1.0 and its my daily driver in the form of Ubuntu 13.04 right now - usually I use Mint but I wanted to eliminate as many variables as possible) but I don't know much about Android.
Admittedly, I started with UT before I had ever worked with CM even so I've learned a LOT. lol

Thanks for this.

So does this kernel work with the latest UT Developer Preview release? If not I would be willing to help you getting it back up to date even though I'm still a newbie! Thanks in advance for the response.
Sent from my SGH-T999 using xda app-developers app

biohazard said:
So does this kernel work with the latest UT Developer Preview release? If not I would be willing to help you getting it back up to date even though I'm still a newbie! Thanks in advance for the response.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It should work fine with the latest DP. I haven't bothered to update it because the kernel source hasn't really been worked on. They're still focusing all of their work on Google devices.
There isn't a stable kernel for any S3 variant right now.
Sent from my SGH-T999 using Tapatalk 4 Beta

Mmmm, I can't seem to get it to boot at all.
Sent from my SGH-T999 using xda premium

biohazard said:
Mmmm, I can't seem to get it to boot at all.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Make sure you followed the directions exactly, any deviation will cause it not to boot. Also there is no boot screen. What you can do is plug it in to the charger before you boot it - if it fails to boot the phone will power off and take you to the charging screen. If it doesn't, give it a few minutes to load up especially the first boot.
If it fails again, let me know and I'll see about building a new kernel some time this week. As far as I am aware there is no newer kernel source on the Ubuntu side but I can try to build an RC5 based kernel (this is an M1 kernel).
Its worked for everyone else but I can't test it right now because I'm getting ready to go out and need my phone.
Sent from my SGH-T999 using Tapatalk 4 Beta

Alright I see, thanks for all the help. Could you possibly point me to the correct base download, I have tried multiple phablet bases, and I just can't get it to boot for some reason. Thanks in advance for all the help.
Sent from my SGH-T999 using Tapatalk 4 Beta

The international GS3 has working wi-fi.....i know the hardware is completely different but do you think you might be able to look at how they got it working over there?
http://forum.xda-developers.com/showthread.php?t=2315397
Here's the commit that shows how he got wi-fi working: https://github.com/Androguide/andro...mmit/feac1d9af58c2947e0f3f6b6719553be5811ce6d try applying that to init.qcom.rc i would but my computer won't build anything i'm trying to fix it...
Also for github you really just need to post your manifests file and whatever you've modified from the source code. i'm not really a pro with github but i've worked with it quite a lot. They have an awesome tutorial on their website i'd recommend checking out.

Okay Ubuntu made upstream code changes that broke the kernel. Give me a few days and I'll have an update.
Plays2 - that patch *should* work for us as well since we use Broadcom's WiFi just like the international version does (odd that they didn't use Qualcomm's since it came with the SoC but it works in our favor in this instance). Still takes a lot of configuration to get it running though.