Database Develop

[DEV/help is needed][ROM] GB Sense 2.3.3 [v1.2.1 in the second post]

SebastianFM has kindly agreed to provide support to fix issues.
That i think is a fantastic news
so please show your appreciation by thanking for the SFM 3.0.2 Magic|Android 2.3.3|Sense 2.1 ROM
Click to expand...
Click to collapse
I REQUEST/ENCOURAGE ANY DEV OUT THERE WHO WOULD LIKE TO TAKE OVER
OR START A FRESH TO BUILD GB-SENSE ROM PLEASE DO SO,
THIS THREAD IS MAINLY FOR INFORMATION PURPOSE
Click to expand...
Click to collapse
warning/disclaimer:
I am not maintaining this ROM, i have only transported this from SFM 3.0.2 Magic|Android 2.3.3|Sense 2.1
initial attempt was on SenseonFire ROM from wildfire
please don't bother this thread with trivial questions
this ROM is only for testing purpose and inspiration for further development only
I started this, with intention of porting the ROM, only to realize that I am not smart enough to fix most things.
I am not claiming to be dev as i am not, so posting the info for you to proceed or dump the project.
WIP <- working in pause (not work in progress)
I thank
SebastianFM for the first porting, which made possible most of the other device ROMs SFM 3.0.2 Magic|Android 2.3.3|Sense 2.1
all those involved in SenseonFire ROM project on wildfire especially VigiDroid,
and Arco for building an awesome kernel and nFinityGB v1.13 ROM for tattoo and some of the files were taken from this ROM
and dsixda's Android Kitchen
Click to expand...
Click to collapse
The main reason I have opened this thread is, to make you aware of the promising future out there for sense lovers using tattoo
and sow some seeds of inspiration for a dev out there who could fix this for us.
What i did
I took the SFM 3.0.2 Magic|Android 2.3.3|Sense 2.1 ROM used dsixda's Android Kitchen utility to transport and then adjusted few libs and binaries to get the phone started
Used Arco's 2.6.35.14 kernel and files from his nFinityGB v1.13 ROM
and added Robot font from following thread http://forum.xda-developers.com/showthread.php?t=1316156
i moved system/app folder to cache/systemapp and symlinked to system due to less space in system partition
Click to expand...
Click to collapse
things like gps, fm and camera are not working on tattoo, many apps need resizing or font size needs reducing.
when i did benchmarking using cf-bench apk, the score i got was more than 500 close twice to what i got with tatfroyosense. Benchmark done at 633 Mhz max cpu

rom link and snapshots
Download links
SFM port version 1.2.1
mediafire
4shared
Changelog
V1.2.1
Pooled all patches together and few minor changes
V1.2
Few apks resized
ROM is by default Overclocked
framework symlinked from cache partition
wipe cache, data before flashing the ROM
First boot takes about 5-10 mins
Main issues:
GPS
Camera
FM
Media player sound OK - video is white
no notification lights (but button lights OK)
Battery drain - if wifi on
and other issues from user (??)
old versions
SFMportv1.2
http://www.mediafire.com/?uzutj2tura75oyr
SFMportv1.1
http://www.megaupload.com/?d=KXLUD91K
SenseonFire port link
http://www.megaupload.com/?d=UYZ4V0WJ
the rom has edify scripting and is unsigned, could be installed with clockworkmod recovery
Click to expand...
Click to collapse

This is cool. I never expected Tattoo to run anything heavy like this.
Feeling proud of you, man! With tears in my eyes.
Sent from my HTC HD2 with my fast fingers.

Waiting for news!!

Umm well, regarding eth0 and tiwlan0, they are just hardware access points for the required device. The Unix/Linux system often puts all devices as files in /dev/. So when it needs to call a particular device, it calls that file and output to that device is piped back into the file.
So eth0 refers to the Ethernet (Wired LAN) interface, while tiwlan0 is the WiFi (Wireless LAN). The problem with older kernels (ralle.gade) is that they list WiFi as standard wired LAN device. Newer kernels list them properly (Arco's kernel). So its just a matter of changing /dev/eth0 to /dev/tiwlan0 in the wpa_supplicant and other wifi config files and wifi will run as needed. i am saying this as far as what i know about configuring desktop linux.
and about camera and videorecorder, u can get the drivers from CM7 and merge with this. For FM, u could get get drivers from CM7 and replace the HTC FM app with the one from CodeAurora or MIUI.
I am interested to help. But it seems I have got some other priorities to attend to. I will be free after April 2012. Then I will brush up my C++ skills and see if I can help u all.

...
too bad,this rom would be perfect if bt, gps, wifi, camera would working on tattoo...

sunitknandi said:
Umm well, regarding eth0 and tiwlan0, they are just hardware access points for the required device. The Unix/Linux system often puts all devices as files in /dev/. So when it needs to call a particular device, it calls that file and output to that device is piped back into the file.
So eth0 refers to the Ethernet (Wired LAN) interface, while tiwlan0 is the WiFi (Wireless LAN). The problem with older kernels (ralle.gade) is that they list WiFi as standard wired LAN device. Newer kernels list them properly (Arco's kernel). So its just a matter of changing /dev/eth0 to /dev/tiwlan0 in the wpa_supplicant and other wifi config files and wifi will run as needed. i am saying this as far as what i know about configuring desktop linux.
Click to expand...
Click to collapse
I dont think this is issues with old and new kernel, they all had access points as tiwlan0 (fyodor, ralle.gade and arco).
So far to my understanding it is device specific (see below).
Dexter seems to have tweaked the module and wpa_supplicant from ralle.gade's kernel to work with Froyo, i dont know what was changed. to get wifi working
EDIT: eth0 limitation is with hardware used in the device
Devices like: Wildfire, Wildfire S, Icon-G and Explorer -have their the access point setup as eth0 and they all have broadcom chip
while Tattoo, Magic and Hero -have tiwlan0 as the access point and they all seem to TI chip

in that case, lets ask dexter. he can help.

sunitknandi said:
in that case, lets ask dexter. he can help.
Click to expand...
Click to collapse
I asked him, he still hasn't responded...
P.S.
i get this from the logcat: " wifi_load_driver end error 2" and from dmesg i get something like: "firmware_path unknown value"
I researched and foundout that the deire had similar problems, but they had a previously working dirver and just couldn't conect....
So that leaves me nowhere again... (sadface)

Few things that i have't mentioned earlier:
Following are the commands in wpa_supplicant script for tatfroyosense
Code:
/system/bin/insmod /system/lib/modules/wlan.ko
/system/bin/wlan_loader -f /system/etc/wifi/Fw1251r1c.bin -e /proc/calibration -i /system/etc/wifi/tiwlan.ini
/system/bin/wpa_supplicant.bin -Deth0 -ieth0 -c/data/misc/wifi/wpa_supplicant.conf
As it is tiwlan0 interface in Arco's kernel, i have copied wlan_loader, wlan_cu, wpa_supplicant, wpa_cli binaries from nFinityGB rom along with /system/etc/dhcpcd folder and the wifi module. (These are already in the ROM attached)
As some of you might have noticed:
module wont load at boot
so i have tried to execute following commands from shell (they are in the init.rc script except insmod of module)
Code:
/system/bin/insmod /system/lib/modules/wlan.ko
/system/bin/wlan_loader -f /system/etc/firmware/Fw1251r1c.bin -e /proc/calibration -i /system/etc/wifi/tiwlan.ini
/system/bin/wpa_supplicant -Dwext -itiwlan0 -c/data/misc/wifi/wpa_supplicant.conf
module loads fine but then wlan_loader give following error
Code:
rtnl_open: Protocol not supported

Hello mate. Is it possible to provide a github repository with the code?

ntenisOT1948 said:
Hello mate. Is it possible to provide a github repository with the code?
Click to expand...
Click to collapse
I dont think HTC source code out there for sense andriod phones.
The time line for this ROM is as follows:
HTC Salsa was ported to Sapphire
http://forum.xda-developers.com/showthread.php?t=1025330
From Sapphire to wildfire
http://forum.xda-developers.com/showthread.php?t=1067868#13557996
wildfire then updated to this
http://forum.xda-developers.com/showthread.php?t=1269485
From above ROM to this ROM
Following files were taken from nFinityGB v1.13 ROM to this ROM
Code:
Filename Folder
wlan_loader system\bin
wpa_cli system\bin
wpa_supplicant system\bin
vold.fstab system\etc
dhcpcd.conf system\etc\dhcpcd
brf6300.bin system\etc\firmware
brf6350.bin system\etc\firmware
Fw1251r1c.bin system\etc\firmware
tiwlan.ini system\etc\wifi
wpa_supplicant.conf system\etc\wifi
Clockopia.ttf system\fonts
DroidSans-Bold.ttf system\fonts
DroidSans.ttf system\fonts
libwpa_client.so system\lib
copybit.bahamas.so system\lib\hw
gps.bahamas.so system\lib\hw
gps.goldfish.so system\lib\hw
gralloc.bahamas.so system\lib\hw
gralloc.default.so system\lib\hw
lights.bahamas.so system\lib\hw
sensors.bahamas.so system\lib\hw
sensors.goldfish.so system\lib\hw
wlan.ko system\lib\modules
bahamas-keypad.kcm.bin system\usr\keychars
bahamas-keypad.kl system\usr\keylayout
AVRCP.kl system\usr\keylayout
vim system\usr\share
colors system\usr\share\vim
filetype.vim system\usr\share\vim
ftoff.vim system\usr\share\vim
indent.vim system\usr\share\vim
indoff.vim system\usr\share\vim
scripts.vim system\usr\share\vim
blue.vim system\usr\share\vim\colors
darkblue.vim system\usr\share\vim\colors
default.vim system\usr\share\vim\colors
delek.vim system\usr\share\vim\colors
desert.vim system\usr\share\vim\colors
elflord.vim system\usr\share\vim\colors
evening.vim system\usr\share\vim\colors
koehler.vim system\usr\share\vim\colors
morning.vim system\usr\share\vim\colors
murphy.vim system\usr\share\vim\colors
pablo.vim system\usr\share\vim\colors
peachpuff.vim system\usr\share\vim\colors
ron.vim system\usr\share\vim\colors
shine.vim system\usr\share\vim\colors
slate.vim system\usr\share\vim\colors
torte.vim system\usr\share\vim\colors
zellner.vim system\usr\share\vim\colors
VoiceDialer.g2g system\usr\srec\config\en.us\grammars
wlan_cu system\xbin

Great news guys
I got wifi and bluetooth working
As i mentioned the history of the ROM in previous post,
It occured to me, may be i can start fresh from Sapphire ROM
So i went to the follwoing post and started with SFM 3.0.2
http://forum.xda-developers.com/showthread.php?t=1025330
and with rough porting i could get wifi and bluetooth working and i bet gps would also work.
you know it was quick and dirty port (huge size and bad layout),
now we can do proper port with relayout and resizing the framework and would be better ROM

Cool... Keep up the hard work. Once u finish the port, we can get someone to optimise it.

Have you updated the download link? Iwould like to have a look to graphics to know if I can do anything about them.
Edit: I can see you don't. But I'm going to start trying to resize some graphics as a practice for future.

2nd post updated with new rom port
some of the applications are not working and poor layout.
Alternative launcher like adw working fine

I't seems there's many other people waiting for news: http://bbs.hiapk.com/thread-2741601-1-1.html
I don't know if it's chinese, or what!
Enviado desde mi HTC Tattoo usando Tapatalk

sense zero on tattoo
Now that i could port (transport) GB sense, i wanted to have a crack at sense zero (it was to decide which one would be best carry on)
so I did try port Hintay Zero 0.14 (Sense 3.5 Android 2.3.5)
and i could get it booted on Tattoo,
but have to set lcd density to 100, so that you can see launcher work.
But most of other things look decent if it is set to 120.
And you can see that layout and size are bad.
but i have to say it takes lot of memory and gets very slow.
framework moved to cache to make space in system.
takes 10 mins on first boot
here the link
http://www.megaupload.com/?d=X1B721BZ
and snapshots

GbermuG said:
I't seems there's many other people waiting for news: http://bbs.hiapk.com/thread-2741601-1-1.html
I don't know if it's chinese, or what!
Enviado desde mi HTC Tattoo usando Tapatalk
Click to expand...
Click to collapse
Yes, its a chinese forum. Gave a try using BabelFish and Google Translate, but it is very messy.
Text like HTC Tattoo intelligent handset gets HTC Sence 3.0 on Peace Outstanding 2.3. (read as smartphone gets htc sense on android version 2.3)
F**k translators. I preferred to read no more.

sunitknandi said:
Yes, its a chinese forum. Gave a try using BabelFish and Google Translate, but it is very messy.
Text like HTC Tattoo intelligent handset gets HTC Sence 3.0 on Peace Outstanding 2.3. (read as smartphone gets htc sense on android version 2.3)
F**k translators. I preferred to read no more.
Click to expand...
Click to collapse
That's what I can understand using translators: they've tried it, and like it. They thik is smooth and powerfull, but ram memory is low. Someone is asking about Sense 3.0, but the tread is not updated, so they only tried SenseonFire (first port). Simply (as I said), they're waiting.

Speed Tweaks for Blur ROMS

This will only modify what needs to be tweak in the build.prop.
It will not modify anybody else's build.prop work.
This means it can be used after you install a custom ROM and
keep any changes your dev has made to their own build.prop.
I have screen shots of my 3 Mps DSL Line and my LTE.
If it gives any indication about how much more performance gain there is
WiFi gives me up to 2.9 Mbps normally.
LTE gives me close to 30 Mbps normally.
Revision 2:
little less aggressive on the phone itself
little bit better WiFi and LTE speeds
cleaned up TONS of code and named everything!
Also the 2nd version will save a backup so you
can restore your old build.prop if you do not like
the changes that were made from from the tweaks.
AND it should keep the original build.prop.
Mind you, the undoer will only work with version 2.
you can also make a swap file (paging file like windows)
command will be
# busybox mkswap /dev/block/zram0
# chmod 077 /dev/block/zram0
# reboot

how did you install an ULV kernel on your droid 4?

dewhashish said:
how did you install an ULV kernel on your droid 4?
Click to expand...
Click to collapse
through an inti.d script

Won't install
I can't get these to install, using safestrap 3.0. Any ideas what I am doing wrong?

zeroktal said:
I can't get these to install, using safestrap 3.0. Any ideas what I am doing wrong?
Click to expand...
Click to collapse
it has only been tested on SS211.
I believe there are differences in the way it reads
and mounts the partitions...
what does the error say?

Not to sound stupid, but will this work on Eclipse 1.3.4 for D4?
Sent from my DROID4 using xda app-developers app

panamakevin said:
Not to sound stupid, but will this work on Eclipse 1.3.4 for D4?
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
the way It is set it up -should- in theory work with any ROM made for the D4.

Can we get this written for ss305?

jkieffer46 said:
Can we get this written for ss305?
Click to expand...
Click to collapse
yes give me a little while to install and reconfigure for ss3

jkieffer46 said:
Can we get this written for ss305?
Click to expand...
Click to collapse
I have tried and failed miserably! I am no means a "true" programmer BUT
I have a work around for the people with SS3. Although it does involve a
terminal emulator which is free and the Google Play Store link is BAM!
I will make a flashable fix in the morning with instructions on how to do it.
I will also have a screenshot of what to type as well. The script will still do
the same thing as the flashable BUT in the terminal (manual way)

Just ran the .sh
I just modified and ran the SH from the command line. Only had to remove one > per file. Thanks, my speed increase isn't amazing, but its solid. You are Awesome.

Is there a way to flash this in ss305 yet or what

No, I'm sorry, haven't time to work on it. right now the work around is through a shell and reboot
Sent from my DROID4 using xda premium

Ok ill wait. I dont know how to do anything other than flash zips

Does it have any tweaks for GSM/HSDPA? The 3G is really poor on Droid 4.

[ROM][DEV] Ubuntu Touch For B&N Nook Tablet

DISCLAIMER: You should know by now that anything you do can and probably does void warranties, can and may brick your devices, etc etc yada yada.... This is my first ever attempt at a port, second ROM to ever build. The base for this is CM10.1 maintained by the official devs for the B&N Nook Tablet (acclaim), so complete props to everyone who has gone looney to get us here. This port isn't very usable and as such is no daily driver by any means.
I will try to explain the details of building as best as I can remember to anyone who wants to know. I had to comment out certain lines here and there and add my changes below them. Being new to this all, I have yet to set up a git for the sources. I just wanted to get this up as I haven't seen anyone else post this for Nook Tablet. From what I know, this should work for the 8g and 16g as this is based off the Official CM10.1 for us. Again, your risk, there are plenty of ways to unbrick this device and plenty of guides.
Discussion thread:
[ROM][DISCUSSION] Ubuntu Touch B&N Nook Tablet
For those of you just wanting to take it for a spin:
(name change as I am building using two different sets of repos, one with only a local branch based off the cm repos, and my own that I will push updates to)
Download Device Specific Build:
Build 5: ut-cm-20130610-acclaim.zip - 35.72 MB
Older Builds:
(The following builds screen displays stop working for newer Ubuntu fs builds)
Build 4: ubuntu_touch-20130529-acclaim.zip - 35.54 MB
Build 3: ubuntu_touch-20130524-acclaim.zip - 34.94 MB
Build 2: ubuntu_touch-20130513-acclaim.zip - 34.90 MB
Build 1: ubuntu_touch-20130511-acclaim.zip - 34.90 MB
Download Ubuntu FS File:
Saucy is the new Raring
http://cdimage.ubuntu.com/ubuntu-touch-preview/
Installation:
1) put both files on your sdcard by your method of choice
2) go into recovery
3) format data/factory reset <-- NOTE: If you want to save data, new builds should backup stuff, not sure what all though.
4) format system to ensure clean install
5) flash Custom build and flash Ubuntu fs file
6) reboot and pray it works.
After boot up notes:
- May have to push power button to get initial display.
-To get a chroot shell from your computer's terminal:
Code:
$ adb root
$ adb shell
$ ubuntu_chroot shell
- Keyboard does not currently work on Home screens. In Raring I would restart ubuntu-session. I do not see it in Saucy. 2013-06-15: playing around and starting the 'killprocs' service, keyboard worked afterwards.
Code:
[email protected]:/# service killprocs start
- Wifi seems to need a reboot to work correctly currently
- Added a script to change the display size.. If you do not like it or want to mess around with it, you can adjust the display through the chroot by editing the acclaim.conf file. After editing, reboot.
Code:
/etc/ubuntu-session.d/acclaim.conf
Build notes!
Build 5:
- Updated ubuntu sources, resulting display seems fixed for newer builds! (circa June 1st or maybe a little sooner)
- Honestly not sure atm if build 4 has it, but added a script to auto fix the display size (adds acclaim.conf for you), Saucy images seem to not require a reboot, Raring images do (or an ubuntu-session restart).
Build 4:
- Using wpa_supplicant 8 instead of 8_TI
Build 3:
- Wifi works with some terminal junk!
Build 2:
- Videos stopped working for some reason, need to debug.
- Apps no longer force close
- Wifi still down
Build 1:
- It boots
- Display works
- Sound Works
- Videos Work
- No wifi
- All apps force close after a couple of seconds
- No rotation
I'm new to all this git stuff, but figured I'd try it out:
https://github.com/dejello/android_device_bn_acclaim
https://github.com/dejello/android_kernel_bn_acclaim
I will be adding a wiki or readme on the device repo that shows dependencies and other edits needed to build your very own.
-dejello

Build 2! and some pics...

THIS POST IS NO LONGER REQUIRED, but kept for informational purposes
Updated - Build 3 now up!
Wifi seems to be working with some terminal junk. I followed this page as a reference after figuring out the wlan module wasn't being loaded: http://www.omappedia.com/wiki/Mac80211_based_open_source_architecture#Procedure_to_build_WLAN_and_test_on_Ubuntu_FS
NOTE: The module is apparently being unloaded after a while, possibly to do with going to sleep, not sure atm. If you have installed the terminal core app you can get back online without plugging back in..
I did the following commands and checked the browser and I was online!
Code:
[email protected]:/ # adb shell
[email protected]:/ # ubuntu_chroot shell
[email protected]:/# sudo mount -t proc proc /proc
[email protected]:/# lsmod
[I]Module Size Used by
wl12xx 189125 0
mac80211 384303 1 wl12xx
pvrsrvkm_sgx540_120 336017 34
cfg80211 181275 2 mac80211,wl12xx
compat 2718 0 [/I]
Notice: It did not show wl12xx_sdio - which has wlan0.
Code:
[email protected]:/# insmod /system/lib/modules/wl12xx_sdio.ko
[email protected]let:/# tail -3 /var/log/kern.log
[I]May 25 23:23:09 ubuntu-phablet kernel: [ 377.563903] wl12xx_set_power: 1
May 25 23:23:10 ubuntu-phablet kernel: [ 377.900939] wl12xx_set_power: 0
May 25 23:23:10 ubuntu-phablet kernel: [ 377.911682] wl12xx: loaded[/I]
[email protected]:/# ifconfig wlan0 up
[email protected]:/# tail -3 /var/log/kern.log
[I]May 25 23:25:04 ubuntu-phablet kernel: [ 492.360870] wl12xx_set_power: 1
May 25 23:25:05 ubuntu-phablet kernel: [ 492.839141] wl12xx: firmware booted (Rev 6.3.10.0.133)
May 25 23:25:05 ubuntu-phablet kernel: [ 492.864288] ADDRCONF(NETDEV_UP): wlan0: link is not ready[/I]
[email protected]:/# iwconfig wlan0 essid "tinyguest"
[email protected]:/# dhclient wlan0
[email protected]:/# ip addr
[I]......
7: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 58:67:1a:53:b1:bd brd ff:ff:ff:ff:ff:ff
inet 192.168.2.13/24 brd 192.168.2.255 scope global wlan0
inet6 fe80::5a67:1aff:fe53:b1bd/64 scope link
valid_lft forever preferred_lft forever[/I]
Note: "tinyguest" is my test guest network with no security atm, insert the SSID of your network. I have not tested yet to see if this will work with security on.
Not sure how stable everything is, but hey, it's a dev preview so
UPDATE: I just had a realization.... After insmoding wl12xx_sdio.ko and bring the wlan0 up, I simply restarted the network manager service and now the gui shows up! I do need to check my wpa_supplicant file as I had been playing with it. <-- Fine unedited. I am also running a new minidroid build compiled using wpa_supplicant 8 vs wpa_supplicant 8_TI that I have yet to upload. I will need to see if this has any effect. I was having an issue compiling the TI version and was getting annoyed trying to figure it out New commands are as follows:
Code:
[email protected]:/ # adb shell
[email protected]:/ # ubuntu_chroot shell
[email protected]:/# insmod /system/lib/modules/wl12xx_sdio.ko
[STRIKE][email protected]:/# ifconfig wlan0 up[/STRIKE] <-- DIdn't even up it this past time, seems that restarting the network-manager service up's it.
[email protected]:/# service network-manager restart
Will be updating this post and adding a pic..

Doing great . Keep up. And why not tranfering it to nt dev thread?
Στάλθηκε από το Barnes & Noble Nook Tablet μου χρησιμοποιώντας Tapatalk 2

demetris_I said:
Doing great . Keep up. And why not tranfering it to nt dev thread?
Στάλθηκε από το Barnes & Noble Nook Tablet μου χρησιμοποιώντας Tapatalk 2
Click to expand...
Click to collapse
Thanks nothing in comparison to what you've been up to lately though. I probably should see about getting this thread moved over shouldn't I....

I'm really excited, I hope your project takes off in a big way
I admit to confusion, though - you say the base of this is the great work done on cm10.1 nightlies by the devs here, so is this actually ubuntu touch, or a skin over android? I'm not being critical, just looking to understand.
Thanks!

tmoulder said:
I'm really excited, I hope your project takes off in a big way
I admit to confusion, though - you say the base of this is the great work done on cm10.1 nightlies by the devs here, so is this actually ubuntu touch, or a skin over android? I'm not being critical, just looking to understand.
Thanks!
Click to expand...
Click to collapse
Sorry for the late reply, yes, currently Ubuntu Touch is running in a chroot on a mini build of android.
Other notes, today I started trying to figure out what exactly breaks the display on the newer ubuntu fs images.
dmesg shows ubuntu-session terminating with: "terminated with status 139". I still have an image from May 24th that works, and upon updating libplatform-api1-hybris or ubuntu-platform-implmentation-android (both of which will install the other) the display breaks with ubuntu-session terminating with: "terminated with status 127" or depending on what I've done ocassionally some other error.
More searching to follow....
UPDATE: see Build 5 notes, I hadn't fully updated my ubuntu sources apparently Display seems to work now!
PS - the git stuff isn't current atm, but the edits should still work. the wiki dealio needs work.

dejello said:
Sorry for the late reply, yes, currently Ubuntu Touch is running in a chroot on a mini build of android.
Other notes, today I started trying to figure out what exactly breaks the display on the newer ubuntu fs images.
dmesg shows ubuntu-session terminating with: "terminated with status 139". I still have an image from May 24th that works, and upon updating libplatform-api1-hybris or ubuntu-platform-implmentation-android (both of which will install the other) the display breaks with ubuntu-session terminating with: "terminated with status 127" or depending on what I've done ocassionally some other error.
More searching to follow....
UPDATE: see Build 5 notes, I hadn't fully updated my ubuntu sources apparently Display seems to work now!
PS - the git stuff isn't current atm, but the edits should still work. the wiki dealio needs work.
Click to expand...
Click to collapse
You say build 5 should fix the display not showing? I tried it and the "Current" Saucy phablet image and got nothing.
I'm about to try the Raring image and see if it works...

ajbiz11 said:
You say build 5 should fix the display not showing? I tried it and the "Current" Saucy phablet image and got nothing.
I'm about to try the Raring image and see if it works...
Click to expand...
Click to collapse
Nope...Saucy bootloops...I don't know how to get a logcat through fastboot, will look it up...

there was a period recently where they were breaking things alot with changes... I have a working version I can upload, but if they update hybris and/or the platform-api again it'll break until i update the build.
Sent from my SCH-I510 using xda app-developers app

Nook HD?
Great work! Any idea if you might get around to making a similar build for the Nook HD/HD+?

iCello said:
Great work! Any idea if you might get around to making a similar build for the Nook HD/HD+?
Click to expand...
Click to collapse
That is in my plans as I just got the HD+, not sure just yet as to when.. I need to pm verygreen or someone else and see what all I need to build cm10.1 first as I am missing something. Once I get a working build I will work on Ubuntu.
Sent from my SCH-I510 using xda app-developers app

dejello said:
That is in my plans as I just got the HD+, not sure just yet as to when.. I need to pm verygreen or someone else and see what all I need to build cm10.1 first as I am missing something. Once I get a working build I will work on Ubuntu.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
Alright, sounds good!

iCello said:
Alright, sounds good!
Click to expand...
Click to collapse
Ok, seems I just wasn't paying attention.. Replaced the boot image in the zip with the apparent non-sdcard version >.> CM10.1 booted so I will work on a build in a bit. For the moment though the tv is calling me

Are you planning non starting a new thread for ubuntu on the HD+?
Sent from my Nook HD+ using Tapatalk 2

Not sure atm.. If not I will update the title of this one
Sent from my SCH-I510 using xda app-developers app

So... if the Ubuntu will be available for HD+, changing a pair of things would make it for HD, is it correct?
Thank you!

dejello said:
That is in my plans as I just got the HD+, not sure just yet as to when.. I need to pm verygreen or someone else and see what all I need to build cm10.1 first as I am missing something. Once I get a working build I will work on Ubuntu.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
I would love this on my Nook HD (not HD+), I have ubuntu installed on all of my systems and love it over windows.
Sent from my Nook HD using XDA Premium HD app

Once I get working builds again (with the new stuff they've added for booting) I will build one for the HD for which I will need testers as I do not have an HD. Honestly did not really work on it today as I am really tired. Looks like I managed to get that one build in before they added this stuff.

dejello said:
Once I get working builds again (with the new stuff they've added for booting) I will build one for the HD for which I will need testers as I do not have an HD. Honestly did not really work on it today as I am really tired. Looks like I managed to get that one build in before they added this stuff.
Click to expand...
Click to collapse
I'll gladly test a build for Nook HD
Sent from my Nook HD using XDA Premium HD app

[PATCH][TX][DEV]kexec hardboot port - dual-boot possible

!!!!!! NOT FULLY TESTED !!!!!!!
This patch is based on Tasssadar's hardboot patch for mako. And I borrowed some code (hardboot page address usage) from alvinhochun's Xperia M port. The kernel source is 9.2.A.0.295 from Sony. Thanks all of above!
Here is Tassadar's original thread which explains what is kexec hardboot and what it does. Apply this patch to your kernel source and it will be capable of booting another kernel/system without reflashing.
Note: KEXEC_HB_PAGE_ADDR doesn't need to be a certain value. In my tests, 0x88000000 and 0x88A00000 both work. However, I don't know if there are significant side effects... There is no ram_console entry in /proc/iomem... The default address calcuated by original patch is 0x88CE0000,which doesn't work, so I removed the calculation code and hardcoded the address (thanks alvinhochun)
Click to expand...
Click to collapse
Usage can be seen in the sh file attached. Sh file is modded on Tasssadar's. Kexec binary is also taken from his github. Thanks again!
Parameters:
--load-hardboot : load the kernel with hardboot request
--initrd : ramdisk path (For 2012 line, that's the ".cpio.gz" file)
--mem-min : where the kernel should be loaded to (lowest address). This is not certain,either. 0x82000000, 0x85000000 both work. You can try different values. (Is there any limitation to this? Plz tell me...) Normally 0x82000000 will be okay.
--command-line : command line for the guest kernel. Note that the arguments appended by bootloader (semcandroidboot.babe1324 etc)need to be added here manually.
Click to expand...
Click to collapse
Now I have successfully dual-booted stock 4.3(205) and OmniROM 4.4 (homemade):
1. re-partition external sdcard to 4 parts. 1 for regular data storage(mmcblk1p1), 1 for /system (mmcblk1p4), 1 for /data (p2) and 1 for /cache (p3).
2. mount /dev/block/mmcblk1p4 to USB storage in TWRP and "dd if=(9.2.A.1.205 system.ext4 extracted from FTF) of=(USB storage)" on computer. You can use a card reader also.
3. modify the fstab files in stock 205 ramdisk to change the devices for /system, /data and /cache. If you want to add recovery, edit their fstabs also. (PERMISSIONS FOR THESE FILES ARE REALLY IMPORTANT! All .rc and fstab should be 644, root:root. Otherwise it won't boot)
4. repack the ramdisk. Push the zImage and ramdisk to the phone and execute the sh file. The phone reboots and stock 4.3 loads.
5. rebooting the phone will go back to host ROM.
Click to expand...
Click to collapse
But there is one problem: in stock 4.3, Baseband is shown as "Unknown" and the phone gets no signal. On the host ROM, it works properly. It seems to be related to TA reading, but I can't think of anything wrong with this...Logcat shows three TA units were missing. But in host ROM, they are shown as missing too. Full logcat attached in zip. I didn't touch any file other than fstab, fstab.qcom and init.target.rc in 205 ramdisk. Stock 4.1 works like a charm though.
Anyone knows? Thanks in advance~

You said you had a Omnirom for tx (homebuild)... Could you share it... If it's stable?
Sent from my LT29i using XDA Premium 4 mobile app

alanc.1996 said:
You said you had a Omnirom for tx (homebuild)... Could you share it... If it's stable?
Sent from my LT29i using XDA Premium 4 mobile app
Click to expand...
Click to collapse
New build arrived (2014/05/21). See the separate thread. Following is the old message.
==================
At least it won't reboot ramdomly..but there may be some minor bugs.
Link: http://pan.baidu.com/s/1i3Hq4ip (Password: kpnn)
Internet connection is not very good here so uploading to devhost/mediafire is nearly impossible...
You need to flash the kernel first, then use the recovery to flash the ROM, then flash the kernel again. After system boots, push the modules file to /system/lib/modules
This is based on tital's port. Thanks a lot~
Later I will open a thread to introduce this ROM...

Cool! Will try it out!
Sent from my LT29i using XDA Premium 4 mobile app

Months ago, when I restored an Nandroid backup of 9.2.A.0.295, the same problem appeared. But at that time only mobile service was dead, while WiFi worked. Now mobile service and WiFi are all dead. The screen stops at "Turning on Wi-Fi". However, in dmesg & lsmod, I can see that WLAN driver module has been loaded, with MAC address changed correctly...And in Service Menu(*#*#SERVICE#*#*), Configuration in Service info is dead. Tapping on it will cause the app to stop responding. What is the point?

OK I tried 9.1.B.1.67 firmware. Everything works, including baseband, Wi-Fi and *#*#SERVICE#*#*... However, it's not so attractive as stock 4.3...

Possible to run this way Doomlord custom kernel (based on stock 205) from stock ROM (PureXT etc)?

RpRAUC said:
Possible to run this way Doomlord custom kernel (based on stock 205) from stock ROM (PureXT etc)?
Click to expand...
Click to collapse
As long as the kernel matches the ROM (phone operates normally when you install the custom kernel as usual), it should be okay...

Is it your plan to keep this TX exclusive, or would you be willing to port this to T?
Great work!
Sent from my LT30p using XDA Free mobile app

Galcactus said:
Is it your plan to keep this TX exclusive, or would you be willing to port this to T?
Great work!
Sent from my LT30p using XDA Free mobile app
Click to expand...
Click to collapse
This patch may work on T without any modification, except for the macro name in memory.h

Has there been any further development on this?
Sent from my LT30p using XDA Free mobile app

Galcactus said:
Has there been any further development on this?
Sent from my LT30p using XDA Free mobile app
Click to expand...
Click to collapse
It's already perfectly working...

In which case, is there any chance of having a guide on how to use this? A few brief steps outlining which files need to be used where, would be greatly appreciated.
(On a side note is there any chance of a version built especially for the Xperia T? I know that there aren't many differences, but it's better to be safe than sorry).
Much obliged
Sent from my LT30p using XDA Free mobile app

Galcactus said:
In which case, is there any chance of having a guide on how to use this? A few brief steps outlining which files need to be used where, would be greatly appreciated.
(On a side note is there any chance of a version built especially for the Xperia T? I know that there aren't many differences, but it's better to be safe than sorry).
Much obliged
Sent from my LT30p using XDA Free mobile app
Click to expand...
Click to collapse
This is a little bit complicated... but I'll try to make a post about this in a few days.
The kernel commits should be the same for TX and T :
https://github.com/updateing/androi...mmit/3d4950e7d3a0cc1549e82fda6c1d961f83e04f4a
https://github.com/updateing/androi...mmit/8843e01fb1b6752768056589a510a2f8985c0884

First 4.2 kernel

Well I got permission from zarboz to use this kernel, but having problems with WiFi. Tried with sun_dream sense 5. Tried wiping cache and factory reset still same problem going to try on stock. Well tried on medusa Rom same problem. Must be in kernel. Any help would be appreciated and welcomed.
https://www.dropbox.com/s/rzsbypd1ft758ir/Myst_4.2.zip?dl=0
Sent from my HTC first using XDA Free mobile app

The more info we can gather the easier it will be to find a fix for this. So if someone can test this out and give us some feedback, thank you very much .

Is there any other kernel for this phone that has WiFi working? Maybe I could try to get the WiFi piece from the good one and put it into this one.

The medusa and sense 5 would I just replace all WiFi references.
Sent from my HTC first using XDA Free mobile app

blafree64 said:
The medusa and sense 5 would I just replace all WiFi references.
Sent from my HTC first using XDA Free mobile app
Click to expand...
Click to collapse
after flashing this kernel, could you do this for me:
1. Flash UKM http://forum.xda-developers.com/android/software/zip-synapse-script-universal-kernel-t2736986
2. Install "synapse" (its an app), reboot
3. Go into synapse, you should now be able to configure the kernel (if you still cant, refer to the link above).
4. Post screenshots of EVERYTHING
5. Upload your build.prop (/system/)
i wish i had a first i could go through the file system myself.
Edit:
Hopefully stock android filesystems stay the same from version to version. im on 5.0 at the moment on my nexus but try some of these things too:
1: delete this folder /data/misc/wifi/ And /data/misc/dhcp and system/etc/wifi reboot. (try deleting 1, then reboot, then if it doesnt work, delete the first 2 folders, reboot, if that doesnt work, delete all 3. try different combos).
(and/or)
2: force stop Bluetooth Share (i think you can go to apps>all> and find it there. reboot
3: drain the battery to 0. like make sure the thing is DEAD and wont boot even into recovery. let it sit for some time. plug in your charger and turn it on at the same time.
here is some additional info. if you want to try this. go right a head!
jpsflores said:
Hello all!
I registered here so that i could share a possible solution to the stuck wifi problem. On my nexus the BT was also stuck most of the time.
Been having the problem for about two weeks and was about to do a clean install and, if the problem persisted, call Google support. Thing is, I had the feelling it was software related and that the hardware was ok.
I´m not sure if BT, Wifi and NFC use the same hardware but the fact was that wifi worked for a few days, BT for a few more and NFC was always functional.
I did some extensive research thru the web and it seemed that this problem was not nexus unique and seemed to be related with wpa_supplicant.conf or wpa_supplicant in the bin file.
On this page, mind you the text is pretty old and not entirely android related:
http:_//_blog.linuxconsulting.ro_/2010/04/porting-wifi-drivers-to-android._html (I can't post links yet so just copy past and remove spacing)
I found this little snippet that caught my attention:
Seems that you can add ap_scan=1 to your wpa_supplicant.conf depending on the drivers you have.
After some more research on the subject of ap_scan i found that:
It seems that addind ap_scan=1 imposes that wpa_supplicant.conf handles the scanning and AP selection. IF there's something wrong with the driver, and not with wpa_supplicant as i originaly thought, this could bypass the problem.
So I added ap_scan=1 just before the device identification lines in wpa_supplicant.conf, reeboted, and now the wifi and bluetooth toggle normaly. I've tried ap_scan=0 (the driver handles the scanning) and the problem returns, so ap_scan=1 does allow you to toggle the wifi and BT on.
I can't yet verify that the phone actually connects to a wireless network and has the same stability and range as before as I'm at work and there's no wireless here.
Therefore I ask for your help to verify this "fix" and thoughts on this.
Sorry if the post is a mess. Both english and programming aren´t my native languages...
My device is a Nexus 5 with stock 4.4.4 KitKat and root.
Greets.
---------- Post added at 10:29 AM ---------- Previous post was at 09:46 AM ----------
So, quick update:
Managed to find an wireless network around and connected to it. Some time later, no sure how much, the phone rebooted.
Some time after that the wifi and Bt were stuck again. Accessed wpa_supplicant.conf and deleted the new wireless network information. Rebooted and all was functional again.
Seems the fix is incomplete as any rewrite of the wpa_supplicant.conf reinduces the initial problematic behaviour...
____________________ Extra Update_______________________
Ok, so it seems that the wpa_supplicant.conf is suposed to have ap_scan=1 by default.
After boot and when I connect to a wifi network my file resets and shows without ap_scan=1 and instead of:
ctrl_interface=wlan0
its
ctrl_interface=data/misc/wifi/sockets
Wifi with a conf. like this never works. If I manualy "correct" the file and reboot, the wifi toogles on, but after a wifi connect gets busted up again.
by now I've done:
- copy wpa_supplicant (the bin file) from a stock 4.4.4
- Check file permissions for all wpa_supplicant files
- dirty flash the stock build (it's my original build so less harm done i guess)
- 2 Clean installs
- 6 factory resets
And the problem persists.
I've called google support and they are sending a new phone as we speak. Now I'm not sure if it's a software or hardware problem (maybe a combination of the two?) but I figured it would be better to reroll a device instead of trying to fix this one as this problem is cleary out of my league.
Thank you all!
Click to expand...
Click to collapse

Cannot download synapse playstore is incompatible ugh..
Sent from my HTC first using XDA Free mobile app

This is my kernel that I'm running right now that I maded awhile back is the info right?
Sent from my HTC first using XDA Free mobile app

blafree64 said:
This is my kernel that I'm running right now that I maded awhile back is the info right?
Sent from my HTC first using XDA Free mobile app
Click to expand...
Click to collapse
Yeah all end correct. Try the steps I posted to fixing Wi-Fi hopefully it will work
BTW. Are you running android 4.4? I thought HTC first is only 4.1

I built this kernel awhile back use GCC 4.6 so is it 4.4 cause all works on this kernel
Sent from my HTC first using XDA Free mobile app

blafree64 said:
I built this kernel awhile back use GCC 4.6 so is it 4.4 cause all works on this kernel
Sent from my HTC first using XDA Free mobile app
Click to expand...
Click to collapse
Is everything working?

All things work but I think its a typo because its api level 16 I don't no how to read kernel info like which toolchain is for what android version.
Sent from my HTC first using XDA Free mobile app

blafree64 said:
All things work but I think its a typo because its api level 16 I don't no how to read kernel info like which toolchain is for what android version.
Sent from my HTC first using XDA Free mobile app
Click to expand...
Click to collapse
Alright.
If you need any more help let me know
I'll do my best